- openSUSE Factory

[opensuse-factory] "contrib": Bugzilla integration
by Alexey Eremenko 18 Aug '08

18 Aug '08

Very important topic for "contrib": Bugzilla integration How-to do it properly ? A possible way: 1. allow to open bug-reports/feature-requests against "contrib" in Novell bugzilla 2. Mailing list must be created for "contrib" maintainers (for now we can use factory mailing-list. 3. New opened bugs must be sent by Bugzilla to the mailing-list 4. Maintainer(s), that knows the package best will respond NOTE: This primitive technique may fail if bugs volume will become large. Any better ideas ? -- -Alexey Eromenko "Technologov" --------------------------------------------------------------------- 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] add ext4 file system support to GRUB legacy
by Peng tao 18 Aug '08

18 Aug '08

Hi, all I am a 08' Google Summer of Code student working for opensuse.org mentored by Coly Li. My project is to provide GRUB legacy with ext4 file system support. Since I'm done with coding related work, I have the patch attached (based on http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/s…). With this patch, grub can boot ext4 partitions with extents feature and detect incompatible 64-bit feature. Grub shall fail to read if targeted file is located on blocks beyond 32-bit offset(which means that /boot partition is larger than 4TB and is very very unlikely in real world) and return ERR_FILELENGTH error with "Error 14: Filesystem compatibility error, cannot read whole file" message. The new grub package is available for tests at http://download.opensuse.org/repositories/home:/bergwolf:/grub4ext4/openSUS… Any suggestions and/or bug-reports are welcome :-) -- RGDS Bergwolf ................ Here lieth one whose name was writ on water.

1 0

[opensuse-factory] Status openSUSE distribution
by Christoph Thiel 15 Aug '08

15 Aug '08

Hi everyone, sorry for the late status update. It will come on time next week, since AJ update his cronjob to remind me of it ;) We are currently facing a number of failing packages (142 on i386, 148 on x86_64), as we move forward to Alpha2. 1/3 of the failing packages are due to a insserv / init script check for Should-Start/Should-Stop (cf. email from Werner on opensuse-packaging). Fixes are being checked in and worked on as I'm writing this. These are the bugs that are blocking an Alpha2 build from happening right now: * libstorage lock issue: https://bugzilla.novell.com/show_bug.cgi?id=416276 * Build0019: Bootloader not working after first reboot https://bugzilla.novell.com/show_bug.cgi?id=417383 * Build0019a: trying to remove openSUSE-release package, which is not installed?! https://bugzilla.novell.com/show_bug.cgi?id=417799 Stay tuned, as we work towards openSUSE 11.1 Alpha2. To be released on Aug 21st. Best, Christoph -- Christoph Thiel, Tech. Project Management, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] A small suggestion regarding RealPlayer.
by Nathan Moschkin 15 Aug '08

15 Aug '08

For those of us who have both KDE and Gnome systems installed, or perhaps even for anyone ... getting RealPlayer to work with audio required that I go tromping through the internet to eventually stumble upon a script that starts RealPlayer under artsdsp (for a couple of reasons, one being that RealPlayer, by default, is launching from a script, now...) Here's the script I found, online. Apparently it's been a problem since version 9... This starts real player using the artsdsp ... it definitely works, and I'm using Gnome as my desktop environment. --- #!/bin/sh # If you don't have readlink, fill in the path to hxplay.bin here. HELIX_LIBS="/usr/lib/RealPlayer10" ; export HELIX_LIBS # To install this script, create a symlink to it from somewhere in your # path. Do *not* move the script out of the HelixPlayer directory, since # it relies on the true location of hxplay to derive the location of the # HelixPlayer directory # REALPLAYSYMLINK and REALPLAYSCRIPT are only used to derive REALPLAYDIR if [ ! -d "$HELIX_LIBS" ]; then REALPLAYSCRIPT="" if [ -h "$0" ]; then REALPLAYSYMLINK=`which $0` # Search for something we can use as readlink READLINK=`which readlink` 2> /dev/null; PERL=`which perl` 2> /dev/null; PYTHON=`which python` 2> /dev/null; if [ -x "$READLINK" ] ; then # echo "Using readlink" REALPLAYSCRIPT=`$READLINK $REALPLAYSYMLINK` elif [ -x "$PERL" ] ; then # echo "Using perl" REALPLAYSCRIPT=`$PERL -e 'print readlink($ARGV[0])' -- $REALPLAYSYMLINK` elif [ -x "$PYTHON" ] ; then # echo "Using python" REALPLAYSCRIPT=`echo 'import os; print os.readlink("/usr/local/bin/hxplay")' | $PYTHON -` else # echo "Using ls (directory name cannot contain spaces)" REALPLAYSCRIPT=`ls -l $REALPLAYSYMLINK | sed -e 's/.* //'` fi else REALPLAYSCRIPT=`which $0` fi if [ ! -x "$REALPLAYSCRIPT" ] ; then echo "Cannot find the HelixPlayer directory." echo "Please set the path in the hxplay script." exit fi # if REALPLAYDIR detection doesn't work, hardcode the directory here REALPLAYDIR=`dirname $REALPLAYSCRIPT` # setup environment # find our common, plugin and codec dlls HELIX_LIBS=$REALPLAYDIR export HELIX_LIBS fi # See if LD_PRELOAD contains any of the sound server libs. If so, remove them. LD_PRELOAD=`echo $LD_PRELOAD | sed -e 's/$[^:]*libesd[^:]*\|[^:]*libarts[^:]*$:\?//g'` export LD_PRELOAD if [ -n "$LD_PRELOAD" ]; then echo "Warning: LD_PRELOAD=\"$LD_PRELOAD\"" fi # execute binary (and pass args), optionally running via catchsegv REALPLAYBIN=$HELIX_LIBS/realplay.bin if [ -n "$DEBUG" -a -x "$CATCHSEGV" ]; then $CATCHSEGV artsdsp $REALPLAYBIN ${1+"$@"} else while /bin/true; do # Restart the player if exit code is 10 artsdsp $REALPLAYBIN "$@" if [ $? -ne 10 ]; then break fi done fi --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] OpenFATE and factory/ 11.X
by Boyd Lynn Gerber 14 Aug '08

14 Aug '08

Hello, Are we going to see openFATE for use with 11.1? I tried to use the test but it would not allow me. I would like to see it and be able to view or add comments. Thanks, -- Boyd Gerber <gerberb(a)zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 3

[opensuse-factory] Czech Packagers Team (Prague) meeting minutes 2008-07-31
by Michal Marek 13 Aug '08

13 Aug '08

Czech Packagers Team (Prague) meeting minutes 2008-07-31 ======================================================== Present: anosek, jmatejek, mmarek, mvyskocil, nadvornik, pgajdos, prusnak, puzel, sbrabec Minutes: mmarek Topics: (1) Vim plugins buildservice project (2) Packages from Rudi (3) Work reports (1) Vim plugins buildservice project Puzel proceeded with his vim plugins project, it currently lives in home:puzel:vim-plugins. It turned out that the biggest problem is which plugins to package (there are hundreds of them), not how to package them. (2) Packages from Rudi We were asked to take maintainership of some packages maintained by ro. Some of the packages already found a new maintainer. (3) Work reports anicka - perl-Tk: investigate failing build - webalizer: update to new 2.20 version and test mvyskocil - merge gnu-javamail to classpathx-mail [bnc#411839] + improved a build of axis to use a classpathx-mail - fix of the build of jakarta-commons-dbcp with javac 1.5.0 (ia64 build problems) puzel - pinentry: closed (bnc#330073) - claws-mail: work on (bnc#407469) * testing, providing info to assignee - adjusting severity & priority of my bugs - vim: (bnc#412889) research and report - research on splashy (Feature #303496) - htop: reported & closed (bnc#413550) - enable per-process IO stats in htop anosek - removed talk client from distribution but it will come back (because ytalk doesn't work with UTF-8) - fixing java packages in Stable prusnak - gnokii: updated to 0.6.26 - kismet: updated to 2008-05-R1 - quagga: updated to 0.99.10 - libGLC: created in OBS (games) - warzone2100: updated to 2.1beta4 (OBS games) - sudo: fixed [bnc#404710] investigate [bnc#402818] - collected env vars for yast2-sudo for kmachalkova - open-vm-tools: fixing build of 2008.07.01, cannot compile with 2.6.26 kernel, reported upstream - xfce4-desktop: created workaround for [bnc#393955] mmarek - updated libwpg, zvbi, sblim-wbemcli - fixed spurious error messages in xawtv/motv (bnc#404034) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] Dropping lilo support from YaST
by Stanislav Visnovsky 12 Aug '08

12 Aug '08

Hi! As some of you've noticed, the bootloader configuration in openSUSE was not in best shape for a couple of releases. Therefore, we plan to drop the support for lilo bootloader from YaST (and thus installation) and leave grub as the only supported bootloader on i386 and x86_64 in openSUSE 11.1. The reason is that there are almost no technical advantages to keep both bootloaders and it makes a lot of sense to focus on a single solution and improve it. As part of this strategy, we also want to document bootloader deployment strategies that are supported by the YaST code and where the users should expect the code to work reliably. The change will mean: 1) YaST bootloader code for lilo will be dropped 2) YaST installation will offer to not install any bootloader, so an experienced user can use this to install lilo manually 3) kernel packages will be unable to adapt lilo configuration automatically, this needs to be done manually after installing a new kernel package Any feedback appreciated. Stano --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

11 22

[opensuse-factory] clock and timezone map ...
by Per Jessen 11 Aug '08

11 Aug '08

This is so minor that I can't find a category in bugzilla ... every time I try to hit "Switzerland" when I click on the world map, I always without exception get "Liechtenstein". On the 2nd map, I get to click Switzerland. Now, why Liechtenstein is even a clickable area on map#1 is beyond me, but I really feel I should be able to hit the somewhat bigger Switzerland ... is it just me and my slowly deteriorating mouse abilities? /Per Jessen, Zürich --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 4

[opensuse-factory] dud
by Peter Czanik 11 Aug '08

11 Aug '08

Hello, I wanted to use a driver update disk, which worked fine for 11.0, but now I get now 'no new driver found' or similar during booting. Is there some kind of time checking (the dud is older than the installer) in linuxrc for dud's, or it is worth for a bug report? Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] Re: [opensuse-project] if the community contributed?
by Per Jessen 10 Aug '08

10 Aug '08

Andreas Jaeger wrote: > There are two aspects to a file system: Is it tested and does it work? > And IMO ext4 gets currently more testing than JFS. But for Novell the > more important question is: Do we have engineers that can fix a bug in > a filesystem? We have those for ext4 but there's nobody for JFS and > that's why it's "officially unsupported - use at your own risk". > Andreas, this is exactly what I'm getting at. You want the community to contribute, but you want to say how and when, primarily because of your support commitments. Well, how about letting the community participate in the support as well? /Per Jessen, Zürich --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2