July 2013 - openSUSE Features - openSUSE Mailing Lists

[openFATE 312568] YaST: add support for systemd service in runlevel editor
by fate_noreply＠suse.de 19 Jul '13

19 Jul '13

Feature changed by: Frederic Crozat (fcrozat) Feature #312568, revision 8 Title: YaST: add support for systemd service in runlevel editor openSUSE Distribution: Evaluation by project manager Priority Requester: Important Requested by: Frederic Crozat (fcrozat) Partner organization: openSUSE.org Description: Yast runlevel editor should be able to detect if systemd is running and allow to enable/disable systemd service (which can shadow some sysvinit services). Relations: - systemd adaptation of YaST (novell/bugzilla/id: https://bugzilla.novell.com/show_bug.cgi?id=664548) https://bugzilla.novell.com/show_bug.cgi?id=https://bugzilla.novell.com/sho… Discussion: #2: Frederic Crozat (fcrozat) (2012-01-06 11:27:40) YaST support (probably adding a service) should talk to systemd using D- Bus API (like it is already done in systemd gtk gui), so it won't have to handle merge of configuration and so on. #3: Andreas Jaeger (a_jaeger) (2013-07-19 11:14:53) Isn't this done already? + #4: Frederic Crozat (fcrozat) (2013-07-19 11:33:27) (reply to #3) + it is : http://kobliha-suse.blogspot.fr/2013/06/yast-runlevel-is-dead-long-live-yas… -- openSUSE Feature: https://features.opensuse.org/312568

1 0

[openFATE 312568] YaST: add support for systemd service in runlevel editor
by fate_noreply＠suse.de 19 Jul '13

19 Jul '13

Feature changed by: Andreas Jaeger (a_jaeger) Feature #312568, revision 7 Title: YaST: add support for systemd service in runlevel editor openSUSE Distribution: Evaluation by project manager Priority Requester: Important Requested by: Frederic Crozat (fcrozat) Partner organization: openSUSE.org Description: Yast runlevel editor should be able to detect if systemd is running and allow to enable/disable systemd service (which can shadow some sysvinit services). Relations: - systemd adaptation of YaST (novell/bugzilla/id: https://bugzilla.novell.com/show_bug.cgi?id=664548) https://bugzilla.novell.com/show_bug.cgi?id=https://bugzilla.novell.com/sho… Discussion: #2: Frederic Crozat (fcrozat) (2012-01-06 11:27:40) YaST support (probably adding a service) should talk to systemd using D- Bus API (like it is already done in systemd gtk gui), so it won't have to handle merge of configuration and so on. + #3: Andreas Jaeger (a_jaeger) (2013-07-19 11:14:53) + Isn't this done already? -- openSUSE Feature: https://features.opensuse.org/312568

1 0

[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

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

09 Jul '13

Feature changed by: Thomas Schmidt (digitaltomm) Feature #72, revision 247 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 +šščřžčřýřáýáí #58: Thomas Schmidt (digitaltomm) (2013-03-04 15:08:47) (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 + #59: Thomas Schmidt (digitaltomm) (2013-07-09 15:44:19) (reply to #9) + 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 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

[New: openFATE 315081] Manual repository release option
by fate_noreply＠suse.de 08 Jul '13

08 Jul '13

Feature added by: Adrian Schröter (adrianSuSE) Feature #315081, revision 1 Title: Manual repository release option Buildservice: Evaluation by engineering manager Milestone: 2.5 Priority Requester: Important Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: OBS already supports to release binaries to another repository via releasetarget definition when using the OBS maintenance support. This feature is also useful outside of maintenance, when a staging repository should be created first and the result shall be released to another repository after testing. Therefore we want to extend current releasetarget definition by a trigger="manual" mode. In addition to that we need a command to execute the release process. For example -X POST /build/$PROJECT?cmd=release or for a specified repo only: -X POST /build/$PROJECT/$REPOSITORY?cmd=release the command will return with "invoked" state after successfully creating the event. -- openSUSE Feature: https://features.opensuse.org/315081

1 3

[New: openFATE 315061] improve YaST installer to allow patterns and packages from network
by fate_noreply＠suse.de 08 Jul '13

08 Jul '13

Feature added by: Tomas Cech (sleep_walker) Feature #315061, revision 1 Title: improve YaST installer to allow patterns and packages from network openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Tomas Cech (sleep_walker) Partner organization: openSUSE.org Description: As you probably already noticed, I'm fighting to get E17 as desktop choice in YaST2 installer. To get E17 choice in installer I need to have pattern and packages present on medium which is already more than full. I proposed replacing LXDE with E17, but there are still users who wants to keep it on medium and I agree, that this shouldn't be the way to fix it. Proper fix I believe is patch YaST2 installer to offer packages and pattern from default repository in http://download.opensuse.org/distribution/ if the network is up. Having checkbox 'Enable network repositories' during installation workflow would make this behavior optional and selected by default if the server is reachable. Business case (Partner benefit): openSUSE.org: I also received feedback from MATE maintainer, who would welcome such option as well and I believe there are others too. This is artificial limitation which should have been removed long time ago. -- openSUSE Feature: https://features.opensuse.org/315061

1 10

[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 315679] Add support for same-partition in bootloader config files
by fate_noreply＠suse.de 04 Jul '13

04 Jul '13

Feature added by: Olaf Hering (olh) Feature #315679, revision 1 Title: Add support for same-partition in bootloader config files Requested by: Olaf Hering (olh) Partner organization: openSUSE.org Description: There should be a way for the installer of the first-stage0 bootloader to work with "relative paths", instead of the current "absolute paths", when it translates config file entries describing disks or partitions. Lets take grub1 as example to show what I mean: Bootloader is supposed to be installed into the root partition. Then /etc/grub.conf has something like setup --stage2=/boot/grub/stage2 --force-lba (hd0,8) (hd0,8) to install the files into partition number #9. Here the "(hd0,8)" should be replaced with something that means "same-partition-where-the-files-are-currently-located-on-the-filesystem". Whatever processes grub.conf then goes and translates this into "partition #9 on the underlying disk". The second part of my grub1 example is /boot/grub/device.map, which currently has something like (hd0) /dev/disk/by-id/ata-WDC_WD15EADS-00P8B0_WD-WMAVU0414744 . This means the given installation is bound to a disk that provides the above identification string. If the underlying storage changes, device.map must be adjusted. But this step can be easily avoided if the code which processes device.map would instead see "(hd0) same-disk-where-the-boot-files-are-on-filesystem" Such changes would make it simple to move an installation around, either by copying the filesystem contents around, or by exchanging the underlying hypervisor. Things like device.map are bound to a given hardware emulation and are not stable as experiance has shown. -- openSUSE Feature: https://features.opensuse.org/315679

1 0

[openFATE 305591] Define Purpose for each openSUSE Build Service Project
by fate_noreply＠suse.de 03 Jul '13

03 Jul '13

Feature changed by: Adrian Schröter (adrianSuSE) Feature #305591, revision 10 Title: Define Purpose for each openSUSE Build Service Project Buildservice: Evaluation by product manager Priority Requester: Important Info Provider: Pavol Rusnak (prusnak) Requested by: Pavol Rusnak (prusnak) Partner organization: openSUSE.org Description: define purpose for each project, like: * add-on package * fresh packages + libraries (eg. games) * bleeding edge packages (eg. zypp:svn) * backports for older distributions (eg. zypp:Backport) * playground (eg. all home projects) So, * this sets users expectations * purpose could be indicated by naming conventions, or even better by project flags * purpose must be shown in the search result for this method to work References: http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00056.html Discussion: #1: Andreas Jaeger (a_jaeger) (2009-08-11 15:51:09) This sounds like a good idea. What needs to be done to make this happen? #2: Adrian Schröter (adriansuse) (2010-02-20 09:25:34) I think we can fullfill this request by two independend features: * Project classification setting to be set by the project owner (this is handled in #306232) * Automatic QA validation how a package will influence the system, for example: * replace base packages * replace files * replace libaries * just being an add-on + #3: Adrian Schröter (adriansuse) (2013-07-03 10:33:49) + The project classification is possible via setting attribute OBS: + QualityCategory to one of the allowed values: + Stable Testing Development Private + However, there is no webui and osc support yet, so this is basically + unused. webui project creation should make it easy to set it and search + in webui/osc/software needs to use it. -- openSUSE Feature: https://features.opensuse.org/305591

1 0