January 2009 - openSUSE Features - openSUSE Mailing Lists

[openFate 305543] software mute not in sync with hardware sync
by fate_noreply＠suse.de 13 Jan '09

13 Jan '09

Feature changed by: Michael Loeffler <michl(a)novell.com> Feature #305543, revision 3 Title: software mute not in sync with hardware sync - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Desirable Requested by: Juergen Weigert (jnweiger) Description: the GUI is not in sync when pressing the mute button in order to unmute the system. Every user who recognizes that the system is not unmuted by pressing the mute button will surely press volume up. Once done, everything is fine again: system is being unmuted in hardware and the GUI is in sync again. it was like this before for ages. bugzilla#389178 was closed as wontfix, as this is not a regression. I'd appreciate that this be fixed some day. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305543

1 0

[openFate 305535] Improve samba yast modules
by fate_noreply＠suse.de 13 Jan '09

13 Jan '09

Feature changed by: Michael Loeffler <michl(a)novell.com> Feature #305535, revision 3 Title: Improve samba yast modules - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Important SLED-11-SP1 SLES-11-SP1 Requested by: James McDonough (jmcdough) Interested: Jiří Suchomel (jsuchome) Interested: Lukas Ocilka (locilka) Description: Improve the design of the yast samba modules. More details to come. References: https://bugzilla.novell.com/show_bug.cgi?id=444603 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305535

1 0

[openFate 305571] Add SystemTap GUI
by fate_noreply＠suse.de 13 Jan '09

13 Jan '09

Feature changed by: Michael Loeffler <michl(a)novell.com> Feature #305571, revision 3 Title: Add SystemTap GUI - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Important SLES-11-SP1 Requested by: Jan Blunck (janblunck) Description: SystemTap GUI is an application intended to ease in the use of the SystemTap tool for Linux. It is both an Integrated Development Environment for the SystemTap scripting language, as well as a data visualization and analysis tool. The GUI is targetted at System Administrators who want to get information out of their system using SystemTap, as well as Developers who wish to write new SystemTap scripts. It is an Eclipse-based application. Relations: - SystemTap GUI Homepage (url: http://stapgui.sourceforge.net/) -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305571

1 0

[openFate 305634] Debian-like dist-upgrade live system full version upgrade
by fate_noreply＠suse.de 13 Jan '09

13 Jan '09

Feature changed by: JP Rosevear <jpr(a)novell.com> Feature #305634, revision 16 Title: Debian-like dist-upgrade live system full version upgrade openSUSE-11.2: Evaluation Priority Requester: Mandatory Requested by: Federico Lucifredi (flucifredi) Interested: Andre Duffeck (aduffeck) Interested: Guy Lunardi (glunardi) Interested: Joe Brockmeier (jbrockmeier) + Interested: JP Rosevear (jproseve) Interested: Klaus Kämpf (kwk) Interested: Matthias Eckermann (mge1512) Interested: Stefan Behlert (sbehlert) Interested: Stephan Binner (beineri) Interested: Thorsten Kukuk (kukuk) Description: With the 11.2 cycle, we want to offer users the ability to perform a live system upgrade in the manner of Debian's dist-upgrade. For the purpose of this cycle, we want to support dist-upgrade from the previous version (11.1) only, as this is a sufficiently complicated problem as is. From the user's view, the difference is between being able to update the system incrementally within the given version or service pack running, to being ble to migrate with a system command ("zypper dup" or similar) to a higher version altogether. In the Debian experience, the set of base distributions is not necessarily limited, but it has been Ubuntu's practice to define what starting points other than "release n-1" are allowed (for instance, all LTS versions are purported to be able to "apt dist-upgrade" to the top of the line, although I have heard of problems trying to jump two years - 6.06->8.10 - in a fell swoop in this manner :-). In the openSUSE scope, we should aim to be able to "dup" between incremental versions, starting from 11.1 to 11.2, and later 11.x to 12.0. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-07 20:42:15) This is the #1 feature in the systems management scope for 11.2 - I have no doubt it will be fun :-) #4: Klaus Kämpf (kwk) (2009-01-09 11:32:53) Passing to mls for technical evaluation (solver + autobuild) #5: Michael Schröder (mlschroe) (2009-01-09 12:48:10) Any hint on what features are currently missing? #6: Klaus Kämpf (kwk) (2009-01-09 13:30:57) (reply to #5) From the top of my head: How to handle * Library ABI changes (e.g. major gcc/g++ upgrades) ? * Core package changes (e.g. devs.rpm to udev) ? * Kernel changes (if application/deamons need a specific kernel abi, dbus comes into mind) ? * Failure handling (network breakdown, package update errors, ...) ? * Booting of the new kernel ? #7: Michael Schröder (mlschroe) (2009-01-09 14:45:09) (reply to #6) And debian does this in some way? -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305634

1 0

[openFate 305634] Debian-like dist-upgrade live system full version upgrade
by fate_noreply＠suse.de 13 Jan '09

13 Jan '09

Feature changed by: Stanislav Visnovsky <visnov(a)novell.com> Feature #305634, revision 15 Title: Debian-like dist-upgrade live system full version upgrade openSUSE-11.2: Evaluation Priority Requester: Mandatory Requested by: Federico Lucifredi (flucifredi) Interested: Andre Duffeck (aduffeck) Interested: Guy Lunardi (glunardi) Interested: Joe Brockmeier (jbrockmeier) Interested: Klaus Kämpf (kwk) Interested: Matthias Eckermann (mge1512) Interested: Stefan Behlert (sbehlert) Interested: Stephan Binner (beineri) + Interested: Thorsten Kukuk (kukuk) Description: With the 11.2 cycle, we want to offer users the ability to perform a live system upgrade in the manner of Debian's dist-upgrade. For the purpose of this cycle, we want to support dist-upgrade from the previous version (11.1) only, as this is a sufficiently complicated problem as is. From the user's view, the difference is between being able to update the system incrementally within the given version or service pack running, to being ble to migrate with a system command ("zypper dup" or similar) to a higher version altogether. In the Debian experience, the set of base distributions is not necessarily limited, but it has been Ubuntu's practice to define what starting points other than "release n-1" are allowed (for instance, all LTS versions are purported to be able to "apt dist-upgrade" to the top of the line, although I have heard of problems trying to jump two years - 6.06->8.10 - in a fell swoop in this manner :-). In the openSUSE scope, we should aim to be able to "dup" between incremental versions, starting from 11.1 to 11.2, and later 11.x to 12.0. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-07 20:42:15) This is the #1 feature in the systems management scope for 11.2 - I have no doubt it will be fun :-) #4: Klaus Kämpf (kwk) (2009-01-09 11:32:53) Passing to mls for technical evaluation (solver + autobuild) #5: Michael Schröder (mlschroe) (2009-01-09 12:48:10) Any hint on what features are currently missing? #6: Klaus Kämpf (kwk) (2009-01-09 13:30:57) (reply to #5) From the top of my head: How to handle * Library ABI changes (e.g. major gcc/g++ upgrades) ? * Core package changes (e.g. devs.rpm to udev) ? * Kernel changes (if application/deamons need a specific kernel abi, dbus comes into mind) ? * Failure handling (network breakdown, package update errors, ...) ? * Booting of the new kernel ? #7: Michael Schröder (mlschroe) (2009-01-09 14:45:09) (reply to #6) And debian does this in some way? -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305634

1 0

[openFate 305634] Debian-like dist-upgrade live system full version upgrade
by fate_noreply＠suse.de 13 Jan '09

13 Jan '09

Feature changed by: Stefan Behlert <behlert(a)novell.com> Feature #305634, revision 14 Title: Debian-like dist-upgrade live system full version upgrade openSUSE-11.2: Evaluation Priority Requester: Mandatory Requested by: Federico Lucifredi (flucifredi) Interested: Andre Duffeck (aduffeck) Interested: Guy Lunardi (glunardi) Interested: Joe Brockmeier (jbrockmeier) Interested: Klaus Kämpf (kwk) Interested: Matthias Eckermann (mge1512) + Interested: Stefan Behlert (sbehlert) Interested: Stephan Binner (beineri) Description: With the 11.2 cycle, we want to offer users the ability to perform a live system upgrade in the manner of Debian's dist-upgrade. For the purpose of this cycle, we want to support dist-upgrade from the previous version (11.1) only, as this is a sufficiently complicated problem as is. From the user's view, the difference is between being able to update the system incrementally within the given version or service pack running, to being ble to migrate with a system command ("zypper dup" or similar) to a higher version altogether. In the Debian experience, the set of base distributions is not necessarily limited, but it has been Ubuntu's practice to define what starting points other than "release n-1" are allowed (for instance, all LTS versions are purported to be able to "apt dist-upgrade" to the top of the line, although I have heard of problems trying to jump two years - 6.06->8.10 - in a fell swoop in this manner :-). In the openSUSE scope, we should aim to be able to "dup" between incremental versions, starting from 11.1 to 11.2, and later 11.x to 12.0. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-07 20:42:15) This is the #1 feature in the systems management scope for 11.2 - I have no doubt it will be fun :-) #4: Klaus Kämpf (kwk) (2009-01-09 11:32:53) Passing to mls for technical evaluation (solver + autobuild) #5: Michael Schröder (mlschroe) (2009-01-09 12:48:10) Any hint on what features are currently missing? #6: Klaus Kämpf (kwk) (2009-01-09 13:30:57) (reply to #5) From the top of my head: How to handle * Library ABI changes (e.g. major gcc/g++ upgrades) ? * Core package changes (e.g. devs.rpm to udev) ? * Kernel changes (if application/deamons need a specific kernel abi, dbus comes into mind) ? * Failure handling (network breakdown, package update errors, ...) ? * Booting of the new kernel ? #7: Michael Schröder (mlschroe) (2009-01-09 14:45:09) (reply to #6) And debian does this in some way? -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305634

1 0

[openFate 305491] package names should also be binary names
by fate_noreply＠suse.de 12 Jan '09

12 Jan '09

Feature changed by: Pavol Rusnak <prusnak(a)novell.com> Feature #305491, revision 29 Title: package names should also be binary names openSUSE-11.2: Evaluation Priority Requester: Desirable SLED-11-SP1 SLES-11-SP1 Requested by: Juergen Weigert (jnweiger) Interested: Federico Lucifredi (flucifredi) Interested: Kai Dupke (kdupke) Interested: Marcus Kraft (marcuskraft) Interested: Stefan Behlert (sbehlert) Description: Many packages providing command line applications do so with commands named different than the package Random examples: install cpuset but call cset; install lvm2 but call lvm; install MPlayer but call mplayer, install MozillaFirefox but call firefox, install NetworkManager-kde but call knetworkmanager; install OpenOffice_org but call soffice/ooffice/oowriter I suggest to create one shell script per package, that is named exactly as the package is named, which tells the user how to use the package (unless a binary with that name already exists). This script could point to existing binaries, print documentation, or simply be a symlink to an existing binary if there is one prominent user callable entry point, whatever makes sense. Discussion: #2: Thorsten Kukuk (kukuk) (2008-11-25 05:58:17) Veto. We decided to name RPMs after the name of the upstream package, especially to be in sync with other distributions and don't confuse ISVs and customers completlty. I don't see any benefit for customers, but only disadvantages for everybody. Between, business case for this very cost-intensiv feature is missing. #3: Thorsten Kukuk (kukuk) (2008-11-25 05:59:18) How would you call "pwdutils"? "useradd"? "userdel"? "passwd"? Split them in 100 little RPMs? #10: Thomas Schmidt (digitaltomm) (2008-11-26 12:00:29) This could be added to the command-not-found tool (http://en.opensuse.org/Scout , don't know whether this is available on SLES). When a command is not found, but scout sees a RPM with exactly this name installed it could display a list of the included binaries. This way no packages would need to be changed, it's only an enhancement to command-not-found. #11: Kai Dupke (kdupke) (2008-11-26 12:43:29) (reply to #10) scout is part of the SLES media. Looks like an answer on how to handle this. Not sure if we install this by default. #14: Pavol Rusnak (prusnak) (2009-01-09 15:56:02) (reply to #11) I and mvyskocil are creators and maintainers of scout. All you need to do is to issue (after installing scout of course): $ scout bin firefox repository | binary | path | package --------------------+---------+----------+---------------- zypp (11.1-oss) | firefox | /usr/bin | MozillaFirefox What else needs to be done? #16: Pavol Rusnak (prusnak) (2009-01-09 15:57:33) (reply to #14) I forgot to note that scout is automatically installed in base system in openSUSE 11.1. #17: Juergen Weigert (jnweiger) (2009-01-09 16:43:41) (reply to #11) Hey, thanks for creating scout. This is very helpful. Currently, I can map from binary to package, by using 'scout bin' This feature is about the reverse, mapping from package to binary. Can this be added to scout? Integration with /usr/bin/command-not-found would be very helpful then. E.g. bash$ MPlayer Package MPlayer includes the following binaries: repository | binary | path | package ---------------------------+---------+----------+--------- zypp (Packman Repository) | mplayer | /usr/bin | MPlayer How do we educate our users about the existance of scout? #19: Pavol Rusnak (prusnak) (2009-01-09 17:30:10) (reply to #17) After discussion with Michal, we'll add -p parameter to each module, which will indicate that package name is provided, not search_term. All modules will benefit from that change, not only "bin", so user could also list all java classes from java package and so on. I'm not quite sure about the command-not-found integration. There are some people who don't like the speed of handler and another extra search will add another fractions of seconds. If user wants that feature, he'll just types: $ scout bin -p MPlayer + #20: Pavol Rusnak (prusnak) (2009-01-12 17:58:19) (reply to #19) + I pushed change into scout git repo which adds -p option to all + modules. Updated packages are also available from home:prusnak:scout + repository. Feel free to test. + $ scout bin mplayer + repository | package | path | binary + ----------------+---------+----------+--------- + zypp (packman) | MPlayer | /usr/bin | mplayer + $ scout bin -p MPlayer + repository | package | path | binary + ----------------+---------+----------+---------- + zypp (packman) | MPlayer | /usr/bin | mplayer + zypp (packman) | MPlayer | /usr/bin | gmplayer + zypp (packman) | MPlayer | /usr/bin | mencvcd + zypp (packman) | MPlayer | /usr/bin | mencoder #15: Michael Loeffler (sprudel24) (2009-01-09 15:58:57) (reply to #10) The Scout way sounds like a good solution. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305491

1 0

[openFate 305656] Make hyperlinks from source project names on 'My Projects' page
by fate_noreply＠suse.de 12 Jan '09

12 Jan '09

Feature changed by: Petr Uzel <puzel(a)novell.com> Feature #305656, revision 2 Title: Make hyperlinks from source project names on 'My Projects' page Buildservice: New Priority Requester: Desirable Requested by: Petr Uzel (puzel) + Partner organization: openSUSE.org Description: When I go to 'My Projects' page in OBS, there is a table with requests concerning me at the bottom of the page. For each request, the table contains source project name. I often need to go directly to that project to check the package. This would be much easier, if the project name were hyperlink to the OBS project. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305656

1 0

[openFate 305591] Define purpose for each project
by fate_noreply＠suse.de 12 Jan '09

12 Jan '09

Feature changed by: Michal Vyskocil <mvyskocil(a)novell.com> Feature #305591, revision 4 Title: Define purpose for each project Buildservice: New Priority Requester: Important Requested by: Pavol Rusnak (prusnak) + Interested: Michal Vyskocil (mvyskocil) Partner organization: openSUSE.org Description: http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00056.html * 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) - 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 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305591

1 0

[openFate 305534] f-spot should use sqlite3 instead of sqlite2
by fate_noreply＠suse.de 12 Jan '09

12 Jan '09

Feature changed by: Michael Loeffler <michl(a)novell.com> Feature #305534, revision 3 Title: f-spot should use sqlite3 instead of sqlite2 - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Juergen Weigert (jnweiger) + Partner organization: openSUSE.org Description: Currently sqlite2 ist installed per default (at least if user runs gnome). It would be much better to require sqlite3 and to phase out sqlite2 to those applications that really need the old-version- compatibility. f-spot was ported to sqlite3 in version 0.4.2, and supports the latest sqlite-3.6 since version 0.5.0.2. f-spot-0.5.0.3 is shipping with e.g. SLED 11 BETA6 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305534

1 0