May 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 303400] Allow to enable the backend error handler (beh) from the YaST printer module
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #303400, revision 14 Title: Allow to enable the backend error handler (beh) from the YaST printer module openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-07-08 09:39:42 reject reason: Postponing. Priority Requester: Desirable - openSUSE-11.2: Evaluation + openSUSE-11.2: Done Priority Requester: Desirable Requested by: Lars Müller (lmuelle) Description: It should be possible to enable the backend error handler (beh) from the YaST printer module. This is usefull if a network printer isn't always reachable. Think of a printer switched on later than the startup of cups happens. Discussion: #1: Johannes Meixner (jsmeix) (2009-03-27 09:46:06) I wonder why I am not included in such requests? It is already implemented in the new yast printer module for openSUSE 11.1 and accordingly also for SLE11 via the "Connection Wizard". How to use it: 0. Usually one would first set up the queue as usual (i.e. without beh). 1. In case of backend errors and when additionally the default error handling is not what is wanted, one would first try if another CUPS error policy helps. One can change the CUPS error policy in YaST via "Policies". 2. If even another CUPS error policy does not do what is wanted, one could daisy-chain beh: Select the queue and "Edit" it. In the "Modify" dialog select "Connection Wizard" and therein "Daisy-Chain Backend Error Handler (beh)" usually leave the defaults for beh (or adapt them, read the help text in YaST), klick "OK" to go back to the "Modify" dialog. Now there is a new connection using "beh" available. Select this new connection in the "Modify" dialog and klick "OK" to apply the change to the queue. -- openSUSE Feature: https://features.opensuse.org/303400

1 0

[openFATE 302573] Make auto-selected-packages popup configurable
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #302573, revision 9 Title: Make auto-selected-packages popup configurable openSUSE-11.0: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-03-27 15:37:25 reject reason: Postponing to be considered for future YaST swmgmt UI changes. Priority Requester: Desirable openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-07-07 12:53:40 reject reason: More important tasks to solve. Priority Requester: Desirable openSUSE-11.2: Evaluation Priority Requester: Desirable + Projectmanager: Desirable Requested by: Lukas Ocilka (locilka) Description: YaST Packager has a special popup after the the list of selected packages is accepted. This popup says something like: These packages were automatically added to the list of packages: * package A * package B Some think that it is a bug and such popup should not appear at all (and packages should be added without asking), some think that it is a nice feature. Having it configurable, e.g., [x] Do not show this dialog again should be good enough for both. Note: this touches both installation and running system, so if decision is made in the installation, it should be copied to the installed system as well. References: Bug 298565 - package selector shouldn't ask about installing more packages (https://bugzilla.novell.com/show_bug.cgi?id=298565) -- openSUSE Feature: https://features.opensuse.org/302573

1 0

[openFATE 305623] Remove gnomesu dependancies from YaST
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #305623, revision 8 Title: Remove gnomesu dependancies from YaST openSUSE-11.2: Evaluation Priority Requester: Mandatory + Projectmanager: Mandatory Requested by: Federico Lucifredi (flucifredi) Description: The Gnome team informs me gnomesu is obsoleted. We need to stop depending on gnomesu on YaST, ideally moving towards PolicyKit as much as possible but at a minimum matching the current mainline Gnome behavior. -- openSUSE Feature: https://features.opensuse.org/305623

1 0

[openFATE 305682] Implement the possibility to allow Add-on source from remote "Plain RPM directory"
by fate_noreply＠suse.de 28 May '09

28 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #305682, revision 5 Title: Implement the possibility to allow Add-on source from remote "Plain RPM directory" openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Stefan Assmann (assmannst) Partner organization: openSUSE.org Description: During installation when configuring an add-on product there is an option called "Local Directory". If you choose that the next window will have a checkbox "Plain RPM Directory" which allows to add a directory that only contains RPMs as an add-on source. Unfortunately this seems not to be available if you try to configure an add-on product that is not stored locally. Neither FTP, HTTP, SMB, NFS etc... have an option to add a "Plain RPM Directory". This is really useful for exchanging single or multiple RPMs during development without the need to wait for the next development snapshot to verify changes made to the RPMs install fine. Support for this should be implemented into autoyast as well. Gives the opportunity to automatically configure a plain rpm update add-on source for easy exchange of RPMs. Business case (Partner benefit): openSUSE.org: Improves development process because developers can test the influence of their changes to RPMs during installation without having to wait for the next development snapshot. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-26 19:43:30) This is nice candy for developers. Good idea. + #2: Christoph Thiel (cthiel1) (2009-05-28 14:30:47) (reply to #1) + I'm unsure if remote plain rpm dirs make much sense. Directory listing + + getting the metadata would be a pain. How about adding a hint on how + to simply create a remote repo with just a few RPMs in there by running + "createrepo" on that directory? -- openSUSE Feature: https://features.opensuse.org/305682

1 0

[openFATE 303534] Extend BarGraph Widget
by fate_noreply＠suse.de 27 May '09

27 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #303534, revision 29 Title: Extend BarGraph Widget openSUSE-11.2: Evaluation Priority Requester: Desirable + Projectmanager: Neutral Requested by: Arvin Schnell (aschnell) Requested by: Matthias Eckermann (mge1512) Description: The latest mockups for the partitioner contain an BarGraph with additional features: * legend * several areas with same color/legend * a bit small (maybe not so important) Here is a picture (http://w3.suse.de/~aschnell/bg2.png) from the mockup. Relations: - Enhance partitioner to be more user friendly (novell/bugzilla/id: 390213) https://bugzilla.novell.com/show_bug.cgi?id=390213 - Graphical Display of Hard Disk partitions (novell/bugzilla/id: 414322) https://bugzilla.novell.com/show_bug.cgi?id=414322 - Blog Comment praising GParted (url: http://lizards.opensuse.org/2009/03/06/context-menus-in-yast-partitioner/#c…) Discussion: #1: Federico Lucifredi (flucifredi) (2008-06-13 15:15:21) Stano, if we need it it is of course M. Let me know, I just have no business reasons, this is entirely an engineering decision. #2: Stefan Hundhammer (sh-sh-sh) (2008-06-17 15:29:07) What's wrong with using the _existing_ widget with its existing features? #3: Stanislav Visnovsky (visnov) (2008-06-17 15:54:05) Agreement is that this is not needed. #4: Katarina Machalkova (kmachalkova) (2009-02-25 16:43:41) Can we please re-consider this for openSUSE 11.2 ? Some visualization of used/free space ratio on the disk/partition, or the whole disk layout in the partitioner overviews would be nice. The problem (not the only one) with current bar graph widget is that if some portion of the graph becomes too small, the text on it is no longer readable. A legend of the graph (as depicted above) would help a lot, but at the very minimum, some tooltips over the graph parts could be added #5: Michael Löffler (michl19) (2009-03-25 17:27:12) (reply to #4) It looks still like an engineering decsion. Stano please re-consider or reject ;-) #6: Arvin Schnell (aschnell) (2009-03-25 17:53:24) (reply to #5) I don't understand why this should be an engineering decision. This feature will directly influence what the users see. It's not a detail hidden deep in source code that makes geeks say "wow" if they should find it while being bored to death. This is a feature users are constantly asking for! #11: Jean-Daniel Dodin (jdd_sysop) (2009-04-08 20:53:33) gparted is much friendly than YaST. shame. jdd #12: FERNANDO RUBEN ESPINOSA RAMIREZ. (fersito) (2009-04-09 04:01:51) You must to do what ever you want Katarina so in order to learn like myself.-fernando (from Leòn GTO. Mexico)greetings. #13: Duncan Mac-Vicar (dmacvicar) (2009-04-09 11:03:22) (reply to #12) This is even a fake email. Final-Recipient: rfc822; ferub(a)att.net.mx Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; host mailin-02.mx.aol.com[64.12.137.89] said: 550 MAILBOX NOT FOUND (in reply to RCPT TO command) #14: Marc Telesha (mtelesha) (2009-05-10 08:03:28) Persoanlly I used a LiveCD of Parted Parted (Gpartitioner) before installing OpenSUSE everytime. It is much easier to do it this way when setting up a dual booting computer.I really think if it had a better GUI for partitions it would make this partitioning easier for people to understand, especially people giving Linux a try.-Marc -- openSUSE Feature: https://features.opensuse.org/303534

1 0

[openFATE 303736] yast and libzypp should respect the disk space reserved for root
by fate_noreply＠suse.de 27 May '09

27 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #303736, revision 9 Title: yast and libzypp should respect the disk space reserved for root openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-07-08 12:18:47 reject reason: Postponing. This is nice to have. Priority Requester: Desirable openSUSE-11.2: Evaluation Priority Requester: Desirable + Projectmanager: Desirable Requested by: Ladislav Slezak (lslezak) Description: If e.g. root partition has 70MB free user space and 500MB free space reserved for root user yast reports 570MB total free space. But installation of a package which is greater than 70MB fails: installing package kdelibs3-devel-doc-3.5.5-45 needs 335MB on the / filesystem Yast should display the non-root free space (70MB in this case). It seems that it is valid only for ext2/ext3 filesystems (XFS and ReiserFS seem to not support root space). Default reserved space for ext2/ext3 is 5%. References: https://bugzilla.novell.com/show_bug.cgi?id=237309 -- openSUSE Feature: https://features.opensuse.org/303736

1 0

[openFATE 303809] Partitioner: allow cloning of disk layouts - was: easier creation of RAID 1
by fate_noreply＠suse.de 27 May '09

27 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #303809, revision 20 Title: Partitioner: allow cloning of disk layouts - was: easier creation of RAID 1 openSUSE-11.1: Rejected by Matthias Eckermann (mge1512) reject date: 2008-07-30 16:50:50 reject reason: Moving to SLE 11 SP 1 / openSUSE 11.2 Priority Requester: Important Projectmanager: Important openSUSE-11.2: Evaluation Priority Requester: Important + Projectmanager: Important Requested by: Matthias Eckermann (mge1512) Description: Proposal is to offer an option in YaST to clone a disk layout for RAID use and probably jump into the RAID-creation-mode directly Below the original request from C. Boltz / openSUSE community: ----------------------------------------------------------------------------------------------------- It would be good to have an easier way to setup a raid 1 (mirroring). Currently you have to: * create partitions on first disk * create partitions on the second disk (usually using the same layout). * put the corresponding partitions (sda1+sdb1, sda2+sdb2, ...) into a raid array. The easier way would be * [x] I want to create a raid 1 * define the partitioning once for both disks YaST should then partition both disks as requested and create the raid volumes This would save the user/admin some time. However, the traditional method should still be available in case someone wants to have a different layout for some partitions for whatever reason. Relations: - Partitioner: allow cloning of disk layouts - was: easier creation of RAID 1 (novell/bugzilla/id: 387373) https://bugzilla.novell.com/show_bug.cgi?id=387373 Discussion: #2: Matthias Eckermann (mge1512) (2008-05-06 20:10:22) Thanks for the proposal. I am happy that there are more people out there sharing my problems:-) Yet, looking at the current "model" we have in mind for partitioner enhancements, I wonder, if we could probably make that more "generic" by adding something like a "clone disk partitioning scheme" button: You would partition hd0 first and then say: please clone this to hd1, hd2, ... and be able to adjust settings on hd1, ... later. Would that fit? so long - MgE #3: Christian Boltz (cboltz) (2008-05-08 05:07:14) Cloning the disk layout sounds like a good idea and would help. To make it more useful for RAID creation, add "clone to md*", maybe combined with a selection dialog to choose the disks to use. #4: Matthias Eckermann (mge1512) (2008-05-08 05:26:16) Well, you know, we indeed are planning to have such a dialog for creation of raids in the future, ...:-) I changed the "title" according to our discussion, and will 1transfer the request into our internal Feature tracking system soon. Thanks! so long - MgE #6: Martin Schmidkunz (mschmidkunz) (2008-05-15 11:37:58) AFAIK it is currently possible to create one partition after the other. So it does not make sense for me to have a "Clone this partition for future use" at the end. Instead I thought of: http://en.opensuse.org/Image:Idea_303809_1.png When the user presses "Add" in the "partitioning" tab he can choose whether to create one new partition or to use the whole partition scheme from another physical harddisk. Does that make sense? #7: Matthias Eckermann (mge1512) (2008-05-15 12:05:53) (reply to #6) Well, no:-( We are not asking for _partition_ cloning, but _disk_ cloning, i.e. if you have several harddisks, and you want to copy the partitioning from sda to sdb or the like. #8: Martin Schmidkunz (mschmidkunz) (2008-05-16 10:01:41) As discussed live with mge we agree on my proposal. #9: Arvin Schnell (aschnell) (2008-05-16 10:33:01) (reply to #8) That approach has some problems: 1) Hiding "Cloning" behind "Add Partition" is incomprehensible. Cloning affect the whole disk, adding a partition not really. 2) The step to select the partition type is omitted if only one type of partition can be selected. 3) The complete workflow of adding a partition is omitted when no partitions can be created. We (mge, mschmidkunz and aschnell) now agreed upon adding an entry to the "expert" menubutton in the partition overview. #16: Arvin Schnell (aschnell) (2009-02-04 11:08:08) Summarising the request: Add a entry "Close disk layout" to the "Expert" button in the disk view. This opens a dialog showing all disks that are suitable for being a clone (constraints: new disks must have equal or larger size). Several disks can be selected. On the selected disks: Delete everything (including RAIDs and LVMs somehow using that disk), create new partition table (if different from existing) and create partitions with same start and sizes (in cylinders as libstorage calculates internally) and partition IDs. Other parameters, e.g. filesystem, are not copied. -- openSUSE Feature: https://features.opensuse.org/303809

1 0

[openFATE 304971] Improved Popup support from libyui
by fate_noreply＠suse.de 27 May '09

27 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #304971, revision 10 Title: Improved Popup support from libyui openSUSE-11.1: Rejected by Stanislav Visnovsky (visnov) reject date: 2008-07-16 09:22:38 reject reason: Not needed anymore. Priority Requester: Desirable Projectmanager: Desirable openSUSE-11.2: Evaluation Priority Requester: Desirable + Projectmanager: Desirable Requested by: Arvin Schnell (aschnell) 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. Relations: - missing linebreak in german YaST2 partitioner message (novell/bugzilla/id: 190817) https://bugzilla.novell.com/show_bug.cgi?id=190817 Discussion: #1: Gerald Pfeifer (geraldpfeifer) (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) (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) (2008-07-16 10:18:29) Why isn't this needed anymore? What do we have instead? -- openSUSE Feature: https://features.opensuse.org/304971

1 0

[openFATE 306237] yast textmode: displaying release notes
by fate_noreply＠suse.de 27 May '09

27 May '09

Feature changed by: Christoph Thiel (cthiel1) Feature #306237, revision 9 Title: yast textmode: displaying release notes - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Desirable + Projectmanager: Desirable Requested by: Karl Eichwalder (keichwa) Description: In YaST ncurses UI, even if the screen is large (more than 100 characters), do not use more than 79/80 width for displaying the frame containing the release notes text. Lines longer than 80 characters are hard to read. Relations: Discussion: #2: Gabriele Mohr (gabi2) (2009-03-25 14:41:44) I have discussed with Karl. The problem also exits for Qt. Therefore a change in YCP layout is necessary. I have attached a suggestion for a layout change in inst_release_notes.ycp. I have used `Empty and `HWeight to add a margin at the left and right side of the text. This approach works for Qt and ncurses. Karl agrees that a stretchable text (width changes depending on total size) is better than a fix width. #4: Karl Eichwalder (keichwa) (2009-03-25 15:16:03) (reply to #2) Thanks, Gabi! > Karl agrees that a stretchable text (width changes depending on total size) is better than a fix width. Yes, at least, it looks better for normal use cases. The patch will probably improve the readability for most users. #3: Gabriele Mohr (gabi2) (2009-03-25 14:43:38) Added attachment patch for inst_release_notes.ycp (HWeight.diff) -- openSUSE Feature: https://features.opensuse.org/306237

1 0

[openFATE 302485] sync GPT and MBR on MacBook (mactel)
by fate_noreply＠suse.de 27 May '09

27 May '09

Feature changed by: Eddy Figueroa (efiggy) Feature #302485, revision 33 Title: sync GPT and MBR on MacBook (mactel) openSUSE-10.3: Rejected by Stephan Kulow (coolo) reject date: 2007-10-01 12:11:18 reject reason: not done from what I heared Priority Requester: Important Projectmanager: Important openSUSE-11.0: Rejected by Stephan Kulow (coolo) reject date: 2008-04-28 09:46:04 reject reason: lacking parted maintainer for the moment Priority Requester: Mandatory Projectmanager: Important openSUSE-11.1: Done Priority Requester: Mandatory Projectmanager: Important openSUSE-11.2: Done Priority Requester: Mandatory Requested by: Ruediger Oertel (oertel) Description: on multiboot setups on MacBooks and other mactel machines, using a combination of GPT and MBR is pretty common (and necessary if you either want to use grub or are also using Windows) for installation on these machines we need to offer a way to sync the GPT to the MBR whenever a change to the GPT is made. There exists a patch for parted to do just this (see bugzilla#220839) and also the sources of refit (refit.sourceforge.net, tool gptsync). Relations: - GPT partitioning and boot support (feature/id: 303026) - fully support disks with GPT (feature/id: 303924) Discussion: #1: Stephan Kulow (coolo) (2007-08-01 12:37:33) sounds like a dataloss we should fix for 10.3 too #2: Edith Parzefall (emapedl) (2007-08-01 17:42:46) We need to find out more about what actually needs to be done, before we can consider making an attempt for 10.3 despite the approaching deadline. #3: Edith Parzefall (emapedl) (2007-08-07 11:53:32) There's not enough time left, please reject for 10.3. #4: Ruediger Oertel (oertel) (2007-11-06 12:29:36) for reference, the patch for parted is in bug#220839. This patch adds the method "map_gpt_to_msdos" to parted and was written by Olaf Hering and discussed on the parted mailing list in May 2007. #5: Duncan Mac-Vicar (dmacvicar) (2008-02-04 21:29:52) Olaf, you wrote the patch, can you please describe us what is exactly needed so YaST makes this kind of configuration to work? There is little knowledge about this situation and we imagine adding the patch to parted is not the only required step. Some additional code in YaST and while setting up the bootloader might be required. Do you know about it? #6: Olaf Hering (olh) (2008-02-18 10:04:25) (reply to #5) There are comments in the patch. Once the GPT partitioning is done, map one GPT partition to a primary msdos partition. yast2-storage knows what the boot partition is, so it can force the mapping. #7: Arvin Schnell (aschnell) (2008-04-03 17:11:26) Duncan asked me to summarise the task for implementation: 1) Include parted patch "parted.msdos-on-gpt.patch". Thomas saw the risk of breaking parted by this. Issue for parted maintainer (we have none). 2) Add new calls to parted to establish the mapping from GPT to MSDOS disk labels. Issue for yast2-bootloader and/or yast2-storage. 3) Fix bootloader config to not call "parted ... boot on" when it's already on. Should fix the update problem Rudi has. Issue for yast2- bootloader. AFAIS not required with patched parted. #8: Duncan Mac-Vicar (dmacvicar) (2008-04-14 11:43:17) Coolo, points 1 and 3 call for reject until bootloader situation and parted one is better. #9: Joachim Plack (jplack) (2008-04-28 12:30:48) michl@ : AFAIK The MacBooks are to date not handled as a supported platform. But they should be last but not least due to there pretty wide spread of that thingy. Please check, define and prioritize. Thanks. BTW there are some booting issues involved #10: Michael Loeffler (sprudel24) (2008-04-28 13:36:54) (reply to #9) That's a clear "nice to have" feature. Needed ressources and involved risks need to be low. #11: Stephan Kulow (coolo) (2008-06-12 12:39:54) (reply to #10) I'm not so sure about this. Depending on what market you look at, you get a market share of 10 - 50 percentage. I didn't fail to notice that Saturn Fürth's laptop departement is basically built around macbooks. #12: Duncan Mac-Vicar (dmacvicar) (2008-07-25 17:21:19) Please reject for 11.0. All resources allocated with mandatory features already. #13: Duncan Mac-Vicar (dmacvicar) (2008-07-25 17:46:29) (reply to #12) meant SLE11/openSUSE11.1 #14: Alexander Graf (algraf) (2008-08-22 19:54:25) (reply to #13) For openSUSE 11.1 / SLES11 it's done already. I checked in a patch for parted a while ago. #15: Stephan Kulow (coolo) (2009-04-22 14:22:43) (reply to #14) opening to openfate to have a link #16: Lars Vogdt (lrupp) (2009-05-13 12:43:12) (reply to #14) For me it doesn't look like "done already". I've a MacBook Pro here and tried to install openSUSE 11.1 without success. FYI: I'm using rEFIt as "bootloader" here - and after each installation, rEFit tells me that the MBR and GPT is out of sync and can't be repared. With the older openSUSE (10.3) it works with this workaround: http://en.opensuse.org/Installation_on_MacBook_Pro_Intel_(x86) <-- grub is not installed Sadly I need the MacBook for my work, but if you can't find another one, I can run a backup and reproduce my problems for you. + #17: Eddy Figueroa (efiggy) (2009-05-27 03:41:47) (reply to #16) + I can verify that I'm still having the issue here with openSuSE 11.1 + and 11.2 Milestone 1. I've got the MacBook Pro 2,2 (late 2006) model. I + tried to configure the partitions (just a swap and ext3 partition, + nothing special) with gParted and was able to successfully sync the GPT + and MBR tables. Then I installed openSuSE and even though I didn't even + have it format or recreate the partitions my MBR was destroyed; I could + no longer sync the GPT and MBR tables. + If there is a clear, definitive guide on what needs to be done to work + around this issue I would love to see it... I haven't run into anything + that has helped (including the guide that Lars linked to) and I would + really love to see openSuSE running on my MacBook Pro. I don't want to + give up! + Thank you for all your hard work, guys (and gals)! -- openSUSE Feature: https://features.opensuse.org/302485

1 0