November 2008 - openSUSE Features - openSUSE Mailing Lists

[openFate 305146] Use old system network configuration when updating instead of demanding a new one
by fate_noreply＠suse.de 24 Jun '09

24 Jun '09

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305146, revision 1, last change by Title: Use old system network configuration when updating instead of demanding a new one openSUSE-11.2: New Priority Requester: Desirable Requested by: Pacho Ramos <pacho(a)condmat1.ciencias.uniovi.es> Partner organization: openSUSE.org Description: Currently, when I try to update from opensuse 10.3 to 11.0 with DVD and I want to add network repositories, I have to configure again my network for opensuse installer even when it is already configured on my opensuse-10.3 I think that would be much better try to use network configuration from old installation and only ask user if a problem occurs Business case (Partner benefit): openSUSE.org: System update from media: Start installation / Update, select network-based repositories to be used, you will be asked to configure the network. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305146

1 5

[openFate 305272] Definition in the Yast2 samba server module for "workgroup" host
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature added by: Lukas Ocilka <locilka(a)novell.com> Feature #305272, revision 1, last change by Title: Definition in the Yast2 samba server module for "workgroup" host openSUSE-11.2: New Priority Requester: Desirable Requested by: Andreas van dem Helge <andrew(a)joako.net> Partner organization: openSUSE.org Description: Add a definition in the samba server module for "workgroup" host. I.E. in a SOHO it isn't always necessary to setup a true "domain" server, however if there were a set of options for things like "LMB" aka "local master browser" and a quick set of clicks to join a "Workgrp" as a client. this tutorial highlights the amount of script editing that could be avoided if the samba server were more "workgroup" friendly http://www.swerdna.net.au/linhowtolanprimer.html#samba (http://www.swerdna.net.au/linhowtolanprimer.html#samba) References: Originally reported as BNC #420766 (https://bugzilla.novell.com/show_bug.cgi?id=420766) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305272

1 3

[openFate 305170] openFATE test
by fate_noreply＠suse.de 05 Mar '09

05 Mar '09

Feature added by: Michael Loeffler <michl(a)novell.com> Feature #305170, revision 1, last change by Title: openFATE test openSUSE-11.1: Evaluation Priority Requester: Mandatory Requested by: Michael Loeffler <michl(a)novell.com> Partner organization: openSUSE.org Description: test Business case (Partner benefit): openSUSE.org: sdf -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305170

1 5

[openFate 305162] Support Ext4 in Grub
by fate_noreply＠suse.de 18 Jan '09

18 Jan '09

Feature added by: coly li <coyli(a)novell.com> Feature #305162, revision 1, last change by Title: Support Ext4 in Grub openSUSE-11.1: New Priority Requester: Important Requested by: coly li <coyli(a)novell.com> Partner organization: openSUSE.org Description: Ext4 is in upstream kernel already. But since lack of grub legacy supporting, Ext4 can not be used as booting partition. By effort of opensuse's GSoC project, Ext4 stage1.5 is aded into grub legacy. We should consider adding the feature in next opensuse release. Code can be found from http://code.google.com/p/grub4ext4/downloads/list -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305162

1 10

[openFate 303708] [CODE11-GM] Mascot for YaST
by fate_noreply＠suse.de 28 Nov '08

28 Nov '08

Feature changed by: Stanislav Visnovsky <visnov(a)novell.com> Feature #303708, revision 13 Title: [CODE11-GM] Mascot for YaST - openSUSE-11.1: Candidate + openSUSE-11.1: Done Priority Requester: Mandatory Projectmanager: Desirable Requested by: Andreas Jaeger <aj(a)novell.com> Partner organization: openSUSE.org Description: Every successfull product has it's own logo and mascot. We should create and market one for YaST as well, display it prominently on all YaST project pages and also in YaST, e.g. in any About screens or as easter egg. Discussion: #2: Michael Loeffler <michl(a)novell.com> (2008-04-24 12:46:55) I'm fine with that. I think this should come out of the inner YaST circle with some help from design people like Jakub. #3: Michael Loeffler <michl(a)novell.com> (2008-04-24 19:54:31) (reply to #2) And we should inlcude the community on that. Zonker might call for ideas/participation for logo creation on his blog and news.openSUSE. org #4: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-04-25 12:08:16) # zypper moo \\\\\ \\\\\\\__o __\\\\\\\'/_ http://en.wikipedia.org/wiki/Hedgehog -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303708

1 0

[openFate 302354] Split metadata by architecture / modules
by fate_noreply＠suse.de 21 Nov '08

21 Nov '08

Feature changed by: Federico Lucifredi <flucifredi(a)novell.com> Feature #302354, revision 15 Title: Split metadata by architecture / modules Buildservice: New Priority Requester: Desirable openSUSE-11.0: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-03-28 16:28:18 reject reason: Out of resources. The speed of parsing is greatly improved, downloading is still an issue in 11.0. Priority Requester: Important - openSUSE-11.1: Evaluation + openSUSE-11.1: Rejected by Federico Lucifredi <flucifredi(a)novell.com> + reject date: 2008-11-20 19:33:01 + reject reason: postponing unless engineering tells me otherwise. Priority Requester: Important openSUSE-11.2: New Priority Requester: Desirable + SLED-11-SP1: New + Priority + Requester: Desirable + SLES-11-SP1: New + Priority + Requester: Desirable Requested by: Stanislav Visnovsky <visnov(a)novell.com> Partner organization: openSUSE.org Description: All packages are in a single file no matter if they are from different architectures, therefore ZYpp has to download everything Any kind of metadata should be separated by architecture. ZYpp does it for patterns in 10.3, but it is still missing for packages The metadata should be ideally separated by subdirectories and modules. See references on how debian does it References: https://bugzilla.novell.com/show_bug.cgi?id=208452 Discussion: #1: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2007-11-09 16:52:55) This is not true, YaST filter patterns in 10.3. Will edit the feature to represent the real problems #2: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-13 20:22:10) Duncan, do we still need this / have an advantage from it ? if so, lets make it Mandatory. #3: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-06-26 13:17:09) This feature requires: - separate primary.xml files per architecture. 90% effort -> rudi , adrian - tell libzypp to ignore certain pattern or convention ( primary-x86_64. xml ??? ) when downloading -> one liner. It is not much benefit anymore as we are much faster now, but I would recommend pset it to desirable and pass to Rudi and Adrian. #4: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-26 13:20:11) (reply to #3) Adrian, this is something for you. #5: Adrian Schröter <adrian(a)novell.com> (2008-11-06 16:21:18) We have seperate ppc from i586/x86_64 to reduce size. We do not have seperation of meta data yet, but it would not help much anyway, as long as we have no filter on rebuild. All files would change anyway, so the size would be the same. It would actually slow down the process due to multiple downloads. + #8: Federico Lucifredi <flucifredi(a)novell.com> (2008-11-20 19:33:57) + PM-Priority for product openSUSE-11.1 downgraded from mandatory to no + priority: + dropping as suggested by Matthias/Adrian. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=302354

1 0

[openFate 303311] Include Pidgin and the Conferencing Plugin for Pidgin
by fate_noreply＠suse.de 13 Nov '08

13 Nov '08

Feature changed by: Stefan Behlert <behlert(a)novell.com> Feature #303311, revision 13 Title: Include Pidgin and the Conferencing Plugin for Pidgin SLED-10-SP2: Done Priority Requester: Important Projectmanager: Important - SLED-11: Candidate + SLED-11: Rejected by Stefan Behlert <behlert(a)novell.com> + reject date: 2008-11-13 23:47:58 + reject reason: No progress Priority Requester: Important Projectmanager: Important + SLED-11-SP1: Evaluation + Priority + Requester: Important Requested by: Gary Ekker <gekker(a)novell.com> Partner organization: openSUSE.org Description: The Teaming + Conferencing product team from the workgroup BU would like us to include pidgin and the conferencing plugin for pidgin in SLED10-SP2. Discussion: #1: Gary Ekker <gekker(a)novell.com> (2008-02-15 13:37:24) Pidgin was added. We were unable to add the zon-plugin and libicecore as there are still some packaging issues to be worked out for libicecore. libicecore is also not yet ready for x86_64. #3: Stefan Behlert <behlert(a)novell.com> (2008-10-23 16:40:14) Gary, Michael, any news on zon-plugin? + #4: Stefan Behlert <behlert(a)novell.com> (2008-11-13 23:49:29) + No progress here. I'm rejecting this now. + Let's see if we want this for SP1 or if we have EMpathy there anda + differen tsolution. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=303311

1 0

[openFate 301791] "Report a bug" a-la-Safari for Mozilla Firefox
by fate_noreply＠suse.de 13 Nov '08

13 Nov '08

Feature changed by: Stefan Behlert <behlert(a)novell.com> Feature #301791, revision 28 Title: "Report a bug" a-la-Safari for Mozilla Firefox openSUSE-11.0: Rejected by Stefan Behlert <behlert(a)novell.com> reject date: 2008-10-14 10:33:33 reject reason: Clearly not done Priority Requester: Mandatory Projectmanager: Desirable Archs: i386, x86-64 openSUSE-11.1: Evaluation Priority Requester: Mandatory Projectmanager: Important SLED-11: Candidate Priority Requester: Mandatory Projectmanager: Important Archs: i386, x86-64 Requested by: Guy Lunardi <glunardi(a)novell.com> Partner organization: openSUSE.org Description: Apple's Safari web browser introduced a really easy for end-users to report public URLs which didn't render properly in Safari. It would be very nice if we could offer something similar for our Firefox. what you should be able to send: - Once Address URL - Description - Problem: other problem, missing content, imcorrect behavior, incorrect aspect, empty page, unable to load the page or unable to connect. - Send screenshot - Send source code Discussion: #1: JP Rosevear <jpr(a)novell.com> (2008-02-28 23:27:20) How is this fundamentally different from Help->Report Broken Website in 2.0.12> I guess code is not sent nor is the screenshot, but this is all the upstream developers are requesting. Or are you intending submission to bugzilla.novell.com? #2: Guy Lunardi <glunardi(a)novell.com> (2008-03-05 18:26:47) (reply to #1) JP, thanks for pointing this out. The solution is very close right now. What it doesn't support is the sharing information for pages that are 'Intranet-based' and not 'Internet-based'. One of our customer may want to report a problem with Firefox with an homegrown application which the developers looking at the results of this submission can't access. Embedding the results (as MTHML or html source) would be the one missing feature. The other thing is that this content probably goes upstream. Should it come to Novell? #3: Gary Ekker <gekker(a)novell.com> (2008-05-09 10:23:42) Michael, does this like something you could do? Or do we need to find another developer? #4: Michael Wolf <maw(a)novell.com> (2008-05-30 18:27:09) (reply to #3) Not sure yet, but I'll look into it. #6: Gary Ekker <gekker(a)novell.com> (2008-09-11 19:00:59) Proxying this for Michael: It seems like the best thing to do would be to use what's already in place. The reporting functionality can be configured. The source to the reporter contains the following: | pref("extensions.reporter.privacyURL", "http://reporter.mozilla.org/privacy/"); | pref("extensions.reporter. serviceURL", "http://reporter.mozilla.org/service/0.3/"); They can be changed in about:config, presumably sitewide. (This might need to be hooked into the gconf stuff.) So I think it would be a matter of setting up a hypothetical http://reporter.novell.com/ and/or http://reporter.example.com/. The source for the server-side part of the reporter is at hosted on mozilla cvs and can be checked out with "cvs -d :pserver: anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/tools/reporter" The maintainers of said server(s) could then deal with problem reports as seems fit. If we choose in SLED to change the default to the hypothetical http://reporter.novell.com/, it would be trivial to do so via the MozillaFirefox-branding-SLED package. (I don't think this package actually exists yet.) #7: Gary Ekker <gekker(a)novell.com> (2008-09-11 19:01:59) Adding Federico and Stano as we might want to look at this in the context of onstar. #8: Stefan Behlert <behlert(a)novell.com> (2008-10-14 10:34:08) What's the status here? #9: Stefan Behlert <behlert(a)novell.com> (2008-10-24 17:23:17) (reply to #8) Gary, Michael? + #10: Stefan Behlert <behlert(a)novell.com> (2008-11-13 23:46:50) + Guy, we need to reject this as there was no progress. + Gary, could you provide an ECO for that? -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=301791

1 0

[openFate 304971] Improved Popup support from libyui
by fate_noreply＠suse.de 13 Nov '08

13 Nov '08

Feature changed by: Stanislav Visnovsky <visnov(a)novell.com> Feature #304971, revision 7 Title: Improved Popup support from libyui openSUSE-11.1: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-07-16 09:22:38 reject reason: Not needed anymore. Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.2: New Priority Requester: Desirable Requested by: Arvin Schnell <aschnell(a)novell.com> + Partner organization: openSUSE.org Description: Currently writing popups with longer texts is difficult: Line wrapping must be done in YCP and thus cannot take font metrics into account. Using RichText widget is also difficult since it's not possible to know the correct height in advance. What I would like to see is a popup that does line wrapping (preserving parapraphs) and adjusts the height of the whole popup accordingly. The popup width should be a parameter or the popup could find a good ratio between width and height. Discussion: #1: Gerald Pfeifer <gp(a)novell.com> (2008-06-27 19:50:50) I guess this is something to leave for our colleagues in engineering to prioritize, thus labeling neutral for PM. #2: Stanislav Visnovsky <visnov(a)novell.com> (2008-07-01 13:37:34) (reply to #1) Duncan, this is in your team, up to you if you need this. #3: Arvin Schnell <aschnell(a)novell.com> (2008-07-16 10:18:29) Why isn't this needed anymore? What do we have instead? -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=304971

1 0

[openFate 302354] Split metadata by architecture / modules
by fate_noreply＠suse.de 06 Nov '08

06 Nov '08

Feature changed by: Adrian Schröter <adrian(a)novell.com> Feature #302354, revision 13 Title: Split metadata by architecture / modules + Buildservice: New + Priority + Requester: Desirable openSUSE-11.0: Rejected by Stanislav Visnovsky <visnov(a)novell.com> reject date: 2008-03-28 16:28:18 reject reason: Out of resources. The speed of parsing is greatly improved, downloading is still an issue in 11.0. Priority Requester: Important openSUSE-11.1: Evaluation Priority Requester: Important + openSUSE-11.2: New + Priority + Requester: Desirable Requested by: Stanislav Visnovsky <visnov(a)novell.com> Partner organization: openSUSE.org Description: All packages are in a single file no matter if they are from different architectures, therefore ZYpp has to download everything Any kind of metadata should be separated by architecture. ZYpp does it for patterns in 10.3, but it is still missing for packages The metadata should be ideally separated by subdirectories and modules. See references on how debian does it References: https://bugzilla.novell.com/show_bug.cgi?id=208452 Discussion: #1: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2007-11-09 16:52:55) This is not true, YaST filter patterns in 10.3. Will edit the feature to represent the real problems #2: Federico Lucifredi <flucifredi(a)novell.com> (2008-06-13 20:22:10) Duncan, do we still need this / have an advantage from it ? if so, lets make it Mandatory. #3: Duncan Mac-Vicar <dmacvicar(a)novell.com> (2008-06-26 13:17:09) This feature requires: - separate primary.xml files per architecture. 90% effort -> rudi , adrian - tell libzypp to ignore certain pattern or convention ( primary-x86_64. xml ??? ) when downloading -> one liner. It is not much benefit anymore as we are much faster now, but I would recommend pset it to desirable and pass to Rudi and Adrian. #4: Stanislav Visnovsky <visnov(a)novell.com> (2008-06-26 13:20:11) (reply to #3) Adrian, this is something for you. + #5: Adrian Schröter <adrian(a)novell.com> (2008-11-06 16:21:18) + We have seperate ppc from i586/x86_64 to reduce size. + We do not have seperation of meta data yet, but it would not help much + anyway, as long as we have no filter on rebuild. All files would change + anyway, so the size would be the same. It would actually slow down the + process due to multiple downloads. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=302354

1 0