- openSUSE Factory

[opensuse-factory] Test of Factory
by Dominique Leuenberger 22 Aug '06

22 Aug '06

Hi, I wanted finally to have a look at the factory 'release' and contribute with some bug reports (possibly). So my first question: - What's the best way in your eyes to get to the latest factory release? - Can I just install a 10.1 as used and then add the factory inst-source as a repository? A 'rug up' will then most probably install a lot of updated packages. Would this work for tests or will the machine be in a 'strange' state after this? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] Symbolic link /media/cdrom
by Marcel Hilzinger 22 Aug '06

22 Aug '06

My personal feature request for 10.2 set a symbolic link each time a CD/DVD is inserted with /media/cdrom. The link should always point to the last inserted CD/DVD. /media/SUSE_LINUX_10.1 is cool, but its hard to work with CDs on command line and writing documentation for Suse is also very hard. So please let's become cd /media/cdrom true for Suse Linux 10.2. Konqueror,etc should/can still show the label of the disk. -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 7

[opensuse-factory] Network and yast fails after the last update
by Juan Erbes 22 Aug '06

22 Aug '06

Yesterday I made a complete update in the actual 10.2 alpha 3, and could'nt start the dsl connection, I got "pppd died, options error 2". If I try to reconfigure the dsl connection via yast, it closes when reads the configuration. With the network card, yast closes again. I downgrading dbus from *.92 to *.91 and the problem continues. The adsl modem is connected via ethernet. Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 5

[opensuse-factory] SuSEconfig clearance: SuSEconfig.automake
by Christoph Thiel 21 Aug '06

21 Aug '06

Hi everyone, we are in the process of going through all SuSEconfig scripts to assess their value/impact and to analyze different ways of solving the problems those SuSEconfig scripts address. In many case SuSEconfig.* scripts turn out to just be a "cheap solution". Let's try to reduce the number of SuSEconfig scripts to the absolute minimum! And try to find superior solutions! The first case that I'd like to fix is SuSEconfig.automake, which reads: --- #!/bin/sh cat /usr/share/aclocal/dirlist.d/* >/etc/aclocal_dirlist --- There are only two packages that place files in /usr/share/aclocal/dirlist.d/ -- gnome-filesystem and automake itself. To achieve the same, while getting rid of SuSEconfig.automake, I'd like to propose to move the above-named script to %postinstall / %postuninstall of gnome-filesystem and automake. Comments, criticism, better ideas? Regards Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 17

[opensuse-factory] Konsole crash
by Arto Viitanen 21 Aug '06

21 Aug '06

As I told about OpenSUSE 10.2 Alpha 2, it crashed the konsole (KDE terminal emulator). I installed Alpha 3 (I tried to upgrade, but there was some problems on glibc.rpm), and konsole crashes still. Actually Alpha 3 seems to be step to worse, since Firefox crashes also. Also automount (of my external harddisk where I keep my backups) complaint that it will not mount to uid 1001 (the first normal user). I tried as root; same stuff. -- Arto Viitanen Finland --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] simple packaging
by jdd 21 Aug '06

21 Aug '06

may be this is already done somewhere, but is it possible to have a very simple documentation of how to make a openSUSE rpm. All what I have seen is very intimidating (for me, say for many others!). in short, given I have already compiled and running an application on my openSUSE computer, how could I make the others use it? for example, I use daily "makethumb.sh". As it's name say, it's a sh script, GPL and AFAIK not included in openSUSE and it should be, very nice. how can I make it part of the packages? thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 10

[opensuse-factory] Call for discussion: pattern definition language
by Klaus Kaempf 21 Aug '06

21 Aug '06

The current format to define patterns - the .pat file - is rather awkward to use and specific to one type of repository. So I created http://en.opensuse.org/Patterns/Definition_Language to start a discussion on defining a more generic way to describe patterns. Comments welcome ! Klaus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

[opensuse-factory] distmeeting minutes
by Andreas Jaeger 21 Aug '06

21 Aug '06

Here are the minutes from our last meeting, Andreas * PolicyKit/resmgr The upstream Hal authors are preparing to require PolicyKit. PolicyKit is a system daemon, applications ask the daemon about permissions. This is a similar concept as resmgr. The question is how to move forward for our distribution. Will be further discussed next time. * Starting daemons by default A reminder: Daemons will only be started by default from their packages if the dist meeting has approved this. Otherwise the autobuild team is authorized to reject this. PolicyKit is a new daemon, it was approved to be started for now. * Move to GNOME 2.16 Not discussed since nobody involved attended, postponed for next meeting (or discussion via email). * SuSEconfig removal SuSEconfig is currently run after each package installation by YaST and is a huge bottleneck. Some scripts have already been removed and we have to discuss how to move on. The purpose of SuSEconfig was to not run one script several times during package installation but just once at the end. We plan to fix scripts that can be done differently, remove obsolete ones and the autobuild team will not check in new SuSEconfig scripts. A review of scripts showed that some are really obsolete, the first 5 scripts were removed already. We need a superior solution, e.g. some way to do delayed execution. This should also work if just rpm or smart is used. An overview of SuSEconfig is appended below. * update messages general/conditional (e.g. bind) During update of packages they could notify users about changes via email and/or the SuSEplugger (until 10.0, this is not anymore in 10.1). Most of these are outdated and not really usefull anymore and should be removed. The question is how to handle situations like bind where config files get rewritten and the user should be informed if this fails. In general, it is not possible to send emails from rpm install scripts. Most cases could be handled by the release notes but there are cases that cannot and we need a better solution to present this, especially since many people to not read the local emails. * Dropping UP Kernel on i386/x86-64 No objection by the dist meeting. This should be done for Alpha4. * Linker Options and Optimizations LDFLAGS="-Wl,-z relro" is now the default and works fine. The hash table optimization will be enabled in binutils and glibc by default as well. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SUSEconfig has around 4 classes of different scripts, the first two are the most common cases: a) /etc/sysconfig has two types of data. * data read by rc-scripts and used directly there * data used by SuSEconfig and spread over /etc/* or /var/* The second type is handled by one class of SuSEconfig scripts, called "CLASS-A". Solutions: - extend rc-scripts to do this - extend daemons to read /etc/sysconfig - ... b) directory index caches scripts that keep index files in several directories up to date. The underlying problem is that rpm can not trigger based on directory modification, but that's currently not in sight. In many cases SuSEconfig is just the cheap solution. A related problem is, that if you install 10 packages, you don't want to regenerate these indexes 10 times. Solutions: - call individually in each related package (the "install-info way") - error prone - many modifications to many packages (and over again for any change) - extend usage of these index files to update cache themselves - ... This type will be called CLASS-B below. (some of these have also been moved to cron.daily in the past) c) similar to b but generate other filetypes from installed files, usually hacks for special programs CLASS-C d) set a symlink according to installation CLASS-D (probably easiest for a postinstall solution) (modulename) (packagename) (class) SuSEconfig.automake (automake) CLASS-B SuSEconfig.cjk-latex (cjk-latex) CLASS-C SuSEconfig.desktop-file-utils (desktop-file-utils) CLASS-B SuSEconfig.fonts (fonts-config) CLASS-B (mostly) SuSEconfig.gdm (gdm) CLASS-A SuSEconfig.ghostscript-cjk (ghostscript-cjk) CLASS-A? SuSEconfig.gnome-vfs2 (gnome-vfs2) CLASS-B SuSEconfig.groff (groff) CLASS-A SuSEconfig.gtk2 (gtk2) CLASS-B SuSEconfig.guile (guile) CLASS-B SuSEconfig.icu (icu) CLASS-D SuSEconfig.isdn (i4l-base) CLASS-A SuSEconfig.ispell (ispell) CLASS-A/CLASS-D SuSEconfig.kde (kdebase3-NLD,kdebase3-SuSE) CLASS-A SuSEconfig.kdm3 (kdebase3-NLD,kdebase3-SuSE) CLASS-A SuSEconfig.libxml2 (libxml2) CLASS-B SuSEconfig.lyx-cjk (cjk-lyx) CLASS-B SuSEconfig.mailman (mailman) CLASS-A SuSEconfig.news (aaa_base) CLASS-A SuSEconfig.pango (pango) CLASS-B SuSEconfig.pbs (OpenPBS) CLASS-A SuSEconfig.perl (perl) CLASS-B SuSEconfig.permissions (permissions) CLASS-A (special ...) SuSEconfig.postfix (postfix) CLASS-A SuSEconfig.prelink (prelink) CLASS-B SuSEconfig.scim (scim) CLASS-A SuSEconfig.scpm (scpm) ?? (-> rcscript .. ?) SuSEconfig.scrollkeeper (scrollkeeper) CLASS-B SuSEconfig.sendmail (sendmail) CLASS-A SuSEconfig.susehelp (susehelp) CLASS-A(?) SuSEconfig.syslog-ng (syslog-ng) CLASS-A SuSEconfig.tetex (tetex) CLASS-B SuSEconfig.tuxpaint (tuxpaint) CLASS-C SuSEconfig.wdm (wdm) CLASS-A SuSEconfig.words (words) CLASS-A/CLASS-D SuSEconfig.xdm (xorg-x11) CLASS-A SuSEconfig.xjdic (xjdic-indices) CLASS-B SuSEconfig.xpdf (xpdf-tools) CLASS-B(?) Andreas -- Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 0

Re: [opensuse-factory] SuSEconfig clearance: SuSEconfig.gdm & SuSEconfig.wdm
by Dominique Leuenberger 21 Aug '06

21 Aug '06

>>>> Heiko Helmle <heiko.helmle(a)head.de> 08/21/06 2:10 PM >>> >Christian Boltz wrote: >> Hello, >> >> Am Montag, 21. August 2006 11:11 schrieb Christoph Thiel: >>> to proceed with the SuSEconfig clearance initiative, let's take a >>> look at SuSEconfig.gdm and SuSEconfig.wdm. Both of them are used to >>> (re)generate config files, by reading some options from >>> /etc/sysconfig/*. To get rid of those SuSEconfig scripts, their logic >>> needs to be moved to >>> /etc/init.d/xdm, to have it (re)generate the according config files >>> prior to launching gdm or wdm. >>> >>> Comments, criticism, better ideas? >> >> Generating config files every time *dm is started is a bad idea IMHO. >> Reason: It is done _at every boot_ instead of "sometimes" after >> installing packages or alike. So you will speedup SuSEconfig, but slow >> down booting a bit :-( > >It depends. The init scripts could easily detect if the >sysconfig-scripts are newer than the config files (or even md5sum them) >and regenerate them only when needed. I think such a logic has to be inside for sure. But the bootup time should be reduced, not increased imho. What are other Distros doing? Why don't they need anything alike? What is so much more special about the SuSE way that others don't need anything alike? Is it just because of a 'lazy' coding stile for YaST? As YaST is reading / modifyng most of these files afaik. So: why not fix these tools? Cheers, Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

[opensuse-factory] SuSEconfig clearance: SuSEconfig.gdm & SuSEconfig.wdm
by Christoph Thiel 21 Aug '06

21 Aug '06

Hi there, to proceed with the SuSEconfig clearance initiative, let's take a look at SuSEconfig.gdm and SuSEconfig.wdm. Both of them are used to (re)generate config files, by reading some options from /etc/sysconfig/*. To get rid of those SuSEconfig scripts, their logic needs to be moved to /etc/init.d/xdm, to have it (re)generate the according config files prior to launching gdm or wdm. Comments, criticism, better ideas? Regards Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 6