November 2015 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 310848] Allow select multiple in Package Manager (YaST module)
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Mindaugas Baranauskas (embar-) Feature #310848, revision 1 Title: Allow select multiple in Package Manager (YaST module) openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Mindaugas Baranauskas (embar-) Description: Now I can select only 1 or only all packages in YaST package manager. It would be logical to allow to mark several packages (more than 1, not all) by pressing Shift, Ctrl. The marked packages could be manipulated with the same task: I select 3 packages, press right mouse, select to install (uninstall/tabu) these 3 packages. -- openSUSE Feature: https://features.opensuse.org/310848

1 11

[New: openFATE 310896] Consistent Network device naming-Name network interfaces to match chassis labels
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Narendra K - (narendra_k) Feature #310896, revision 1 Title: Consistent Network device naming-Name network interfaces to match chassis labels openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Narendra K - (narendra_k) Partner organization: openSUSE.org Description: On a Dell PowerEdge server with multiple add-in cards, the naming of the network interfaces is non-deterministic. This results in 'eth0' not mapping to "Embedded NIC 1" as labelled on the server chassis. This issue is seen on Dell PowerEdge 10G above. This feature addresses this issue by renaming network interfaces based on the following policy as discussed in the Linux Plumbers Conference - http://marc.info/?l=linux-hotplug&m=128892593821639&w=2 Embedded devices: em<port> (em => ethernet-on-motherboard) Add-in PCI cards: pci<slot>#<port>_<virtual function instance> On a PER710 with 4 Lan-On-Motherboard interfaces and a dual port add-in network controller, the interface names would look like - Onboard interfaces - em1 em2 em3 em4 eth0 Interface names for the dual port add-in controller on pci slot 2 pci2#0, pci2#1 If the second port has virtual functions enabled - pci2#1_0, pci2#1_2 ... etc Biosdevname, which is a Dell developed utility can suggest these names for the kernel ethN names. This needs to be used as a udev helper utility. It is available here - http://linux.dell.com/files/biosdevname/permalink/biosdevname-0.3.1.tar.gz http://linux.dell.com/files/biosdevname/permalink/biosdevname-0.3.1.tar.gz.… GIT: http://linux.dell.com/cgi-bin/gitweb/gitweb.cgi?p=biosdevname.git;a=summary Please find the relevant upstream discussions - * http://marc.info/?l=linux-hotplug&m=129003163201746&w=3 * http://marc.info/?l=linux-netdev&m=129100609428767&w=3 * http://linux.dell.com/files/presentations/Linux_Plumbers_Conf_2010/matt-dom… * http://linux.dell.com/files/presentations/Linux_Plumbers_Conf_2010/matt-dom… Test Case: With this change - 1.ifconfig -a would show emN names for onboard interfaces. 2. em1 should correspond to the interface labelled 'Gb1' on the chassis label, em2 to 'Gb2' etc. This can be tested by ethtool -p em1 (Blinks the interface) 3. If the kernel has the commit 911e1c9b05a8e3559a7aa89083930700a0b9e7ee cat /sys/class/net/em1/device/label Embedded NIC 1 Use Case: System administrators can use the Bios provided names which are consistent across reboots. There is no state such as HWADDR embedded to achieve persistent naming Business case (Partner benefit): openSUSE.org: When there are multiple network interfaces in a system (onboard + add-in interfaces), eth0 does not always map to the 'Embedded NIC 1' as labelled on system chassis. The naming is non-deterministic. This feature request addresses the issue by naming the interfaces as per the BIOS suggested names. Please refer to the following for more details on the reasons for non-determinism * http://lwn.net/Articles/356900/ * http://linux.dell.com/files/presentations/LinuxCon_2010/linuxcon2010_domsch… -- openSUSE Feature: https://features.opensuse.org/310896

1 9

[New: openFATE 312450] Imrpovements on Yast package manager
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Fernando Martin (fernando_a_martin) Feature #312450, revision 1 Title: Imrpovements on Yast package manager openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Fernando Martin (fernando_a_martin) Partner organization: openSUSE.org Description: It's very frustating when I'm downloading packages in yast and something fails and lose all I was downloading. It's also complicated that I have to calculate how long the download of packages will last 'cause I can't pause and resume it later. It would be very nice if the gui yast package manager worked like a download manager allowing pause, resume, restart of failed downloads, preview of size, progress and time and had gui customization for what to do when something fails. -- openSUSE Feature: https://features.opensuse.org/312450

1 2

[New: openFATE 312451] Imrpovements on Yast package manager
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Fernando Martin (fernando_a_martin) Feature #312451, revision 1 Title: Imrpovements on Yast package manager openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Fernando Martin (fernando_a_martin) Partner organization: openSUSE.org Description: It's very frustating when I'm downloading packages in yast and something fails and lose all I was downloading. It's also complicated that I have to calculate how long the download of packages will last 'cause I can't pause and resume it later. It would be very nice if the gui yast package manager worked like a download manager allowing pause, resume, restart of failed downloads, preview of size, progress and time and had gui customization for what to do when something fails. -- openSUSE Feature: https://features.opensuse.org/312451

1 3

[openFATE 306900] Mobile openSUSE portal
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Andrew Wafaa (FunkyPenguin) Feature #306900, revision 1 Title: Mobile openSUSE portal Hackweek IV: Unconfirmed Priority Requester: Important Requested by: Andrew Wafaa (funkypenguin) Description: I aim to complete my previously started openSUSE on Symbian (http://www.wafaa.eu/index.php?/archives/196-openSUSE-on-Symbian.html) portal to work fully with all services, including Bugzilla and Hermes. I will require help with this, particularily with JavaScript. -- openSUSE Feature: https://features.opensuse.org/306900

1 2

[New: openFATE 310504] Gnome Desktop Wallpaper Slideshow.
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Carl Fletcher (caf4926) Feature #310504, revision 1 Title: Gnome Desktop Wallpaper Slideshow. openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Carl Fletcher (caf4926) Description: Gnome is lacking a easy to impliment Desktop Wallpaper Slideshow. KDE offers an easy option of just selecting a folder. Couldn't this be done in gnome? -- openSUSE Feature: https://features.opensuse.org/310504

1 10

[New: openFATE 308896] Add option to automatic update to install all updates, not just patches
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Tim Edwards (tk83) Feature #308896, revision 1 Title: Add option to automatic update to install all updates, not just patches openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Tim Edwards (tk83) Description: The Automatic Update configuration configurable through YAST->Online Update Configuration currently only installs patch updates. An option should be added to install all updates (ie. this would run 'zypper up' without the '-t patches' option). (This new option should be off by default to avoid changing the current behaviour too much.) -- openSUSE Feature: https://features.opensuse.org/308896

1 6

[New: openFATE 312429] submit request templates
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Ludwig Nussel (lnussel) Feature #312429, revision 1 Title: submit request templates Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: when submitting a new package to e.g. openSUSE:Factory packagers are expected to answer some questions: http://en.opensuse.org/openSUSE:How_to_contribute_to_Factory#Adding_a_packa… To make the process more user friendly osc should directly offer a template for the commit message that contains the necessary instructions. Use Case: adding new packages to openSUSE:Factory -- openSUSE Feature: https://features.opensuse.org/312429

1 1

[openFATE 306439] Include Eucalyptus in 11.2
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Andrew Wafaa (FunkyPenguin) Feature #306439, revision 1, last change by Title: Include Eucalyptus in 11.2 openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Andrew Wafaa (funkypenguin) Description: Please could we include Eucalyptus in the next release? For thos unaware of Eucalyptus please see their homepage (http://www.eucalyptus.com/) , and for those that are too lazy to do that - Eucalyptus is an Open Source alternative to Amazon's EC2 Cloud computing offering. This is the very product that Ubuntu are using for their " Ubuntu Enterprise Cloud (http://www.ubuntu.com/products/whatisubuntu/serveredition/cloud/UEC) ". I am not advocating a "jump on the bandwagon" or "keeping up with the jones'" attitude. I am however advocating empowering our distribution and community with the necessary tools to stay ahead of the pack. I can also see several instances where the openSUSE project could potentially benifit from implementing our own cloud - it's no secret that there are some infrastructure constraints, and going down the Utility/Grid/Cloud/$Current_Buzz_Word computing may help things. For those that question whether there is a demand for it, I will admit there may not be a huge demand at the moment. The key thing is if we can market it right (in co-operation with Eucalyptus) we can get a much bigger uptake on both products - even our darling SLE cousin can join in the fun ;-) -- openSUSE Feature: https://features.opensuse.org/306439

1 17

[New: openFATE 309367] Suggest packagekit to quit when it conflicts with yast sw_single
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Atri Bhattacharya (badshah400) Feature #309367, revision 1 Title: Suggest packagekit to quit when it conflicts with yast sw_single openSUSE-11.3: Unconfirmed Priority Requester: Mandatory Requested by: Atri Bhattacharya (badshah400) Description: In response to zypper sending a quit signal to packagekit when packagekitd conflicts with its operation as outlined in Bug 580513 (bugzilla.novell.com) the same should be implemented for the software management module in YaST since it is more visible there and novice users who are most likely to be confused by the conflict in question usually use the GUI more than the command line interface of zypper. -- openSUSE Feature: https://features.opensuse.org/309367

1 3