June 2012 - openSUSE Features - openSUSE Mailing Lists

[openFATE 311297] Get rid of SuSEconfig.groff
by fate_noreply＠suse.de 19 Jun '12

19 Jun '12

Feature changed by: Andreas Jaeger (a_jaeger) Feature #311297, revision 27 Title: Get rid of SuSEconfig.groff openSUSE Distribution: Done Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Michal Svec (msvec) Partner organization: openSUSE.org Description: There is no point to run that code after installation of every package (and it's not run when you use zypper or 3rd party tools anyways). Possible solutions: 1) Fix groff to respect locale settings (LC_PAPER); ideal solution. 2) Add that code to yast2 language (write things during installation and whenever the user changes it later); should be easy to do. 3) Drop SuSEconfig.groff without replacement; unclear consequences. 4) Add that code to yast2 language (write things only during installation), based on comment #1. I would vote for 1, as it's a proper solution. If not doable or not doable with a reasonable effort let's at least do 2. + Relations: + - Remove SuSEconfig (feature/id: 100011) Discussion: #1: Thorsten Kukuk (kukuk) (2011-02-15 13:24:41) Option 1 is for various reason no option. My proposal is based on 2: YaST2 should write /etc/papersize during installation, and only there. Rewriting it later is a bad idea, since the admin could have choosen to change the default. #2: Michal Svec (msvec) (2011-02-15 13:35:25) (reply to #1) Can you elaborate why is 1 not an option? Regarding your proposal it is now changed everytime a new package is installed (unless turned off in sysconfig), so I don't think it would hurt to update it from YaST, but I am fine with both options. #3: Thorsten Kukuk (kukuk) (2011-02-15 13:38:13) (reply to #2) Read the code, the file is not changed if the administrator has modified it. #4: Michal Svec (msvec) (2011-02-15 13:43:49) (reply to #3) OK. And why is 1 not an option? #5: Thorsten Kukuk (kukuk) (2011-02-15 13:49:28) (reply to #4) You don't want to have that code in YaST2, this gives only surprises and is a support nightmare, if YaST2 sometimes changes the config and sometimes not. #6: Michal Svec (msvec) (2011-02-15 14:04:44) (reply to #5) That is clear. I wonder why we cannot go with option 1 (fix groff). #7: Thorsten Kukuk (kukuk) (2011-02-15 14:07:59) (reply to #6) Sorry, misunderstoood. We cannot fix groff because it is not broken. groff has a config file, and that should be honoured. I for example don't want letter output only because I prefer an english locale. #8: Michal Svec (msvec) (2011-02-15 14:11:18) (reply to #7) I would expect you to set LC_PAPER correctly then. But anyways, I can live with option 4. #9: Michal Vyskocil (mvyskocil) (2011-02-15 14:21:42) (reply to #3) SuSEconfig.groff in sle-11-sp1 version overwrites the /etc/papersize everytime - see bnc#644467 (https://bugzilla.novell.com/show_bug.cgi?id=644467) . The fix is easy (I assume the check_md5_and_move is in SLE-11-SP1). So in case you decided to stay with this script, this bug should be fixed. #11: Thorsten Kukuk (kukuk) (2011-05-18 10:09:45) For openSUSE: We can break with everything, so I suggest to remove the SuSEconfig.groff file completly without replacement. Background: groff does not read this file by default, you have to specify it on the command line. For SLE11 SP2 this is not an option, since we don't know if there aren't scripts using that option and expecting that the file exists. #12: Michal Vyskocil (mvyskocil) (2011-06-28 09:17:18) (reply to #11) Removed together with 1.21 update - sent to Factory by request 74706. Marked as done for openSUSE and SLE-12. Release Notes: groff: /etc/papersize No Longer Depends on sysconfig Variables Challenge: /etc/papersize no longer inherits settings from /etc/sysconfig/language when running SuSEconfig. Solution: Set /etc/papersize directly, e.g.: echo "letter" > /etc/papersize For details, see man 5 groff_font ('papersize string'). -- openSUSE Feature: https://features.opensuse.org/311297

1 0

[openFATE 313535] Get rid of SuSEconfig.texlive
by fate_noreply＠suse.de 19 Jun '12

19 Jun '12

Feature changed by: Andreas Jaeger (a_jaeger) Feature #313535, revision 3 Title: Get rid of SuSEconfig.texlive openSUSE Distribution: Evaluation by project manager Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: There is no point to run that code after installation of every package (and it's not run when you use zypper or 3rd party tools anyways). That code should be only run as a part of post-install of the texlive packages as only those are affected. + Relations: + - Remove SuSEconfig (feature/id: 100011) -- openSUSE Feature: https://features.opensuse.org/313535

1 0

[New: openFATE 313542] Make openSUSE the best gnome 3 distro ever
by fate_noreply＠suse.de 19 Jun '12

19 Jun '12

Feature added by: Dmitri Naumov (dnaumov) Feature #313542, revision 1 Title: Make openSUSE the best gnome 3 distro ever openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Dmitri Naumov (dnaumov) Partner organization: openSUSE.org Description: OpenSUSE provided one of the best out-of-box experience with gnome: already configured compiz plugins, special menu, integration with hamster, etc. With gnome 3, it's possible to greatly improve the user experience by the use of extensions. What I suggest is to collect a list of extensions which community finds useful and worth including in openSUSE distribution. Rules: 1. Provide a short description and link to the extension. 2. Proposed extensions must be useful for all users; the fact that you can't live without it isn't enough. 3. No "remove something" extensions allowed. So, I'll start with my list: - Alternative status menu (already there) - Dock https://extensions.gnome.org/extension/17/dock/ Many people complains about complexity of switching between apps in stock gnome-shell. This one fixes this problem, also making it easier for gnome 2 users to migrate to gnome-shell. - Media player indicator https://extensions.gnome.org/extension/55/media-player-indicator/ Show information about currently playing track and allows to control the media player. Similar to that Unity's thing in sound menu. - Advanced Settings in UserMenu https://extensions.gnome.org/extension/130/advanced-settings-in-usermenu/ Many users find it frustrating that gnome-shell can't be configured thorugh the usual preferences interface. I hope gnome devs will fix it soon, but for now it seems reasonable to integrate gnome-tweak-tool in the UI. - Urgent Hint Notification https://extensions.gnome.org/extension/274/urgent-hint-notification/ Displays a shell notification for windows that set the urgent hint - this fixes compatibility problems with some gnome2 apps (namely, xchat) -- openSUSE Feature: https://features.opensuse.org/313542

1 1

[openFATE 305715] Package event framework
by fate_noreply＠suse.de 18 Jun '12

18 Jun '12

Feature changed by: Jan Weber (japa83) Feature #305715, revision 18 Title: Package event framework openSUSE-11.2: Rejected by Andreas Jaeger (a_jaeger) reject date: 2009-06-09 14:44:19 reject reason: We're not going to manage to do this for 11.2. If rpm gets all the changes, we can incorporate this later. Priority Requester: Desirable Requested by: Andreas Gruenbacher (agruen) - Product Manager: Federico Lucifredi (flucifredi) Partner organization: openSUSE.org Description: The installation, upgrade, or removal of several packages triggers actions such as running ldconfig, rebuilding the initrd, or similar. Those actions are not specific to the package at hand, but either global with a system-wide effect (such as running ldconfig), or they affect a group of packages (such as all kernel (sub-)packages of a specific version, including all KMPs affecting it). Those actions need to be run eventually (with order restrictions relative to other package installs, upgrades, or removals), but running them again and again for each package is wasteful. (Example: with the kernel packages split into kernel-$flavor-base, kernel-$flavor, and kernel-$flavor-extra in CODE11, we currently run mkinitrd out of the %post script of each package. We don't know which of those packages will be installed, and when generating the initrd is supposed to succeed. This both wastes time, and we also cannot tell transient from permanent failures.) In former days, SuSEconfig was used for some of those tasks, but it turned into a major nightmare (perhaps due to its design). It would be nice if we could come up with a framework in which packages can trigger events and define which actions they need to be run, and rpm will then perform those actions in an appropriate order, avoiding repeating the same action unnecessarily. (The dependencies between actions and package installs/upgrades/removals are somewhat complex, but I think they are manageable.) Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-23 18:09:34) This is desirable only as it happens within RPM's framework (or if the additions are "candy" that does not affect the actual result). This includes upstreaming. I do not want to comment besides the RPM requirement until Engineering determines how (and if) to proceed. There are too many factors involved. Stano, Needinfo me back when you guys have a settled position or decide to postpone this one given the other priorities. #2: Klaus Kämpf (kwk) (2009-01-29 12:45:22) Actually, there is probably litte engineering can do or decide here imho. It very much depends on PMs long-term strategy for RPM. There are currently two options * One is to stay with rpm 4.x and keep the status quo. * The other is to move up to rpm5 and try to influence its development. Upstream implementation of the feature request can only happen within rpm5. Adopting rpm5 for the distribution has several prerequisites: * Investment into rpm5 development. * Getting more distributions to adopt rpm5. * Influencing Linux Standards Base to accept rpm5. Given recent comments from RedHat/Fedora, widespread rpm5 adoption looks rather unlikely. #3: Michael Schröder (mlschroe) (2009-01-29 12:50:19) (reply to #2) That sounds like rpm-4 doesn't get new features at all, which is simply not true. Actually I think it's probably easier to get new features into rpm-4, because it's very hard to convince Jeff of something he doesn't like, whereas Panu is more open. #4: Klaus Kämpf (kwk) (2009-01-29 13:22:30) (reply to #3) Now thats good to know. But this probably still needs a significant investment (and a fair bit of persuasion) into rpm4, I guess. #5: Casper Clemence (maninalift) (2009-02-28 15:05:35) I don't know about the issue of how the installer works but from a user perspective the handling of multiple kernel flavours could certainly be better. At the moment a symbolic link is automatically created at /boot/vmlinuz pointing, rather arbitrarily IMO, to the most recently updated kernel. Also the grub menu is messed with in an inept sort of a way. If instead symbolic links were created for each kernel flavour there would be no need to change the grub menu except when new flavours were installed or others removed, thus preserving all of the users other boot settings. #6: Klaus Kämpf (kwk) (2009-09-22 12:35:25) The "rpm summit" which was held during the 2009 openSUSE conference brought us a big step forward here. We've now established a healthy relationship with 'rpm4 upstream' and thus will _not_ move to rpm5 anytime soon. Rpm4 will add 'file triggers' in a future version, makeing it possible to e.g. run 'ldconfig' if a library file was installed, updated or removed. A couple of other use cases come into mind for this. --- I'd recommend to close this feature request for now and wait for rpm4 upstream to come up with a solution. -- openSUSE Feature: https://features.opensuse.org/305715

1 0

[openFATE 305552] Support in YaST for public directories in encrypted home directories
by fate_noreply＠suse.de 18 Jun '12

18 Jun '12

Feature changed by: Jan Weber (japa83) Feature #305552, revision 16 Title: Support in YaST for public directories in encrypted home directories openSUSE-11.2: Rejected by Christoph Thiel (cthiel1) reject date: 2009-05-26 18:28:27 reject reason: Postponed for 11.2. Priority Requester: Important - openSUSE-11.3: Rejected by (cthiel1) + openSUSE-11.3: Rejected by Christoph Thiel (cthiel1) reject date: 2010-03-08 16:38:09 reject reason: out of resources for 11.3. Priority Requester: Important Projectmanager: Neutral Requested by: Tim Lee (timl33) - Product Manager: Federico Lucifredi (flucifredi) Partner organization: openSUSE.org Description: A follow on feature to #301923. There should be a way in the YaST users module to specify directories to make accessable in an encrypted home directory when the user is not logged in. See bug #446317. I would suggest an editable list of directories to exclude from the encrypted image, with a reasonable set of defaults. Examples of directories to exclude ~/.vacation, ~/.procmail, ~/.forward, ~/public_html and ~/.ssh References: https://bugzilla.novell.com/show_bug.cgi?id=446317 Discussion: #1: Fco. Javier Nacher (xiscoj) (2010-01-28 12:23:51) hi, maybe if not in yast, it could be like in ubuntu a context menu in kde/gnome over files and folders to encrypt them, like in windows too. So while you are logged they are decrypted to you but when not they are encrypted. Bye #2: Jan Engelhardt (jengelh) (2010-01-31 20:19:16) What's wrong with having a ~/Encrypted subdirectory? You cannot possibly know in advance how many dot-files would need to be readable. To be frank, there are even non-dot-files like ~/public_html that ought to be readable. #3: Jiri Srain (jsrain) (2010-03-04 10:03:03) I don't think that this functionality belongs to YaST. It is decission of each individual user which directories he wants to have public and which encrypted, the administrator can hardly decide this for all users. Please, reevaluate integration into KDE and GNOME instead of YaST. -- openSUSE Feature: https://features.opensuse.org/305552

1 0

[openFATE 313535] Get rid of SuSEconfig.texlive
by fate_noreply＠suse.de 18 Jun '12

18 Jun '12

Feature changed by: Andreas Jaeger (a_jaeger) Feature #313535, revision 2 Title: Get rid of SuSEconfig.texlive openSUSE Distribution: Evaluation by project manager Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) + Partner organization: openSUSE.org Description: There is no point to run that code after installation of every package (and it's not run when you use zypper or 3rd party tools anyways). That code should be only run as a part of post-install of the texlive packages as only those are affected. -- openSUSE Feature: https://features.opensuse.org/313535

1 0

[openFATE 313536] Get rid of SuSEconfig.fonts
by fate_noreply＠suse.de 18 Jun '12

18 Jun '12

Feature changed by: Andreas Jaeger (a_jaeger) Feature #313536, revision 2 Title: Get rid of SuSEconfig.fonts openSUSE Distribution: Evaluation by project manager Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) + Partner organization: openSUSE.org Description: There is no point to run that code after installation of every package (and it's not run when you use zypper or 3rd party tools anyways). That code should be only run as a part of post-install of the fonts packages as only those are affected. -- openSUSE Feature: https://features.opensuse.org/313536

1 0

[openFATE 313537] Get rid of SuSEconfig.glib2
by fate_noreply＠suse.de 18 Jun '12

18 Jun '12

Feature changed by: Andreas Jaeger (a_jaeger) Feature #313537, revision 2 Title: Get rid of SuSEconfig.glib2 openSUSE Distribution: Evaluation by project manager Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) + Partner organization: openSUSE.org Description: There is no point to run that code after installation of every package (and it's not run when you use zypper or 3rd party tools anyways). That code should be only run as a part of post-install of the packages. -- openSUSE Feature: https://features.opensuse.org/313537

1 0

[New: openFATE 312320] don't install postfix by default anymore
by fate_noreply＠suse.de 14 Jun '12

14 Jun '12

Feature added by: Ludwig Nussel (lnussel) Feature #312320, revision 1 Title: don't install postfix by default anymore openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Partner organization: openSUSE.org Description: postfix slows down system boot and runs on every installation even though it's not actually needed anymore on the average desktop. Even mutt can send mails without local mta nowadays. Therefore we shouldn't install postfix anymore by default. cron may need adjustments to report output of cron jobs via other means such as syslog. -- openSUSE Feature: https://features.opensuse.org/312320

1 7

[New: openFATE 309554] Exaile
by fate_noreply＠suse.de 13 Jun '12

13 Jun '12

Feature added by: Hendrik Vogelsang (hennevogel) Feature #309554, revision 1 Title: Exaile Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Hendrik Vogelsang (hennevogel) Description: http://www.exaile.org/ Exaile is a music player aiming to be similar to KDE's Amarok, but for GTK+ and written in Python. It incorporates many of the cool things from Amarok (and other media players) like automatic fetching of album art, handling of large libraries, lyrics fetching, artist/album information via Wikipedia, Last.fm submission support, and optional iPod support via a plugin. -- openSUSE Feature: https://features.opensuse.org/309554

1 3