December 2009 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] 11.2 Release Notes
by Karl Eichwalder 25 Jun '10

25 Jun '10

It would be good if we would start with collection release notes snippets for 11.2 now. Do not hesitate to provide input! Here is some background information: http://en.opensuse.org/Release_Notes -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 1

[opensuse-factory] Kernel Mode Setting (KMS) for openSUSE.
by Egbert Eich 29 Mar '10

29 Mar '10

Folks - In yesterday's discussion about the future of SaX2 it has been requested that changes that will affect users in the future are communicated to the openSUSE community early. KMS (kernel mode setting) integration would be such a feature, thus I would like to announce this here and one step further dive into a technical discussion about a possible solution. Furthermore test packages are available to try things out on Factory. I would like to encourage people interested in development and technical discussions in general to participate in the discussion and the development efforts. Kernel Modesetting (KMS) ======================== All of you who are using a graphical desktop on Linux have been using the X Window Sytem. The X Window System Server (XServer) is the instance which receives requests from your desktop applications to draw all the widgets (windows, buttons, images etc.) you see on your desktop. It also processes input from your keyboard and mouse and sends them to applications as events. Traditionally on Linux the XServer does not only draw images to the screen (ie writes them to some sort of frame buffer) but it is in charge of initializing, setting up and driving the graphics hardware. This paradigm which has been true since the X Window System has been ported to Linux is about to change: Much of the initialization, set up (video mode setting) and control of the graphics hardware is about to move to the Linux kernel. There are a number of advantages to this: - A central instance is in charge of the graphics hardware, other user mode applications (not just the Xserver) can take advantage of mode setting. - The Xserver will no longer require full root privileges as it doesn't talk to the hardware directly any more. - Faster boot process: The Xserver doesn't need to (re)initialize the graphics hardware any more, this is all done by the kernel very early in the boot cycle. - Smoother (flicker free) boot experience: The screen doesn't flicker and changes resolution any more when the Xserver starts. - One central entity is in charge and manages the resources of the graphics hardware - like the video memory which makes sharing of these resources between several applications (like Xserver and several DRI (Direct Rendering 3D) applications much easier. KMS is integrated in the DRM drivers. In the near future most graphics driver will switch to KMS: - Intel already ships a fully working KMS driver. Future Intel chipsets will be supported by the KMS driver only. - KMS in the Radeon DRM driver is still work in progress but it is already working well on some chipsets. - Noveau is relying heavily on KMS for their free 3D driver for NVIDIA chipsets. The proprietary ATI and NVIDIA drivers are unlikely to switch to KMS in the near future. Integration in openSUSE ======================= Now this begs the question what we have to do to integrate it into openSUSE. Originall I had plans to look into this for openSUSE 11.2 already - but then I got side tracked by other stuff it fell on the floor and noone else beat me to it either ... oh well. Now I had the chance to play around with KMS a little and came up with some ideas and a proof of concept. It turned out that the changes to openSUSE needed to fully support KMS are quite small. Key is to load the KMS aware DRM driver as early as possible in the boot process to avoid video mode changes later in the boot cycle - preferrably in the initrd. The Boot Process ---------------- On openSUSE the boot loader is configured for two boot scenarios: default and failsafe. The user can select the failsafe boot scenario in case the default scenario does not work for him. In the failsafe scenario certain features are deactivated which have shown to cause problems on some systems. Since KMS is a new feature it is a candidate for deactivation during a failsafe boot. Instead the system should then boot into the VESA framebuffer mode. Should this also fail the kernel will automatically fall back to a VGA text mode. To disable KMS on boot a new boot parameter is introduced: 'nomodeset'. This parameter is to the boot command line for the failsafe mode. The user may add this parameter by hand for any other boot mode. The kernel command line is parsed in initrd and an appropriate entry is created in /etc/modprobe.d/options. Furthermore the graphics driver module and - if required - the agp module(s) are added in the correct order (agp modules first) to the list of modules to be loaded initially. Changes to individual packages ============================== 1. yast2-bootloader & perl-Bootloader ------------------------------------- The boot parameter 'nomodeset' is added to the failsafe boot paramter lists in each of the modules. (I have not been able to find out which module provides the entry relevant for which situation, therefore I've whacked both.) yast2-bootloader updates the variable FAILSAFE_APPEND in /etc/sysconfig/bootloader appropriately. 2. kernel-source ---------------- To use KMS for a certain DRM driver the kernel config option CONFIG_DRM_<driver_name>_KMS needs to be set to 'y'. At the moment we will support KMS only for Intel hardware, thus only the variable CONFIG_DRM_I915_KMS needs to be changed. In the sample build this has been enabled for the -default, -desktop, -pae, -debug, -trace and -vanilla kernels for the i386 and x86_64 platforms. The kernel boot splash has already been fixed for KMS for openSUSE 11.2. 3. mkinitrd ----------- This package writes the initrd file. To add KMS support to the initrd mkinitrd needs to perform the following tasks: 1. Check the sysconfig variable NO_KMS_IN_INITRD, if set, don't attempt to install a KMS DRM capable driver. 2. Obtain a list of PCI devices installed on the system. 3. a. In the list of PCI devices identify those devices which are of class VGA and look for a matching driver. b. Before a driver is matched check the PCI vendor, device, subvendor and subdevice ids against a blacklist in /etc/kms/blacklist should this file exist. This file contains one vendor, device, subvendor and subdevice id per line, '*' serves as a wildchar, trailing wildchars may be ommitted, '#' at the beginning of a line serves as a comment. c. Use the standard modprobe alias mechanism to find a matching DRM driver module. This way standard blacklistings of kernel modules will be honored and update modules will be searched if they are available. KMS capable DRM drivers provide an alias list (in contrast to non-KMS capable DRM drivers which are to be loaded explicitely by the Xserver). d. If a driver is found check for a black listing in /etc/kms/<driver_name>.blacklist. The same rules as in 3 b. apply. 4. If a KMS capable DRM driver is found search for an agp driver: a. Obtain a list of all known agp drivers for the specific kernel and collect their alias lists. b. Match all installed PCI devices against the alias lists of each agp driver. If a match is found add the driver to the lists of modules to be loaded. Make sure that this driver is loaded prior the the DRM driver. Two scripts setup-kms.sh and boot-kms.sh are added to mkinitrd. The former performs the tasks listed above, the latter provides the required module dependencies in the required order, parses the boot command line for the 'nomodeset' option and adds the apropriate entry to /etc/modprobe.d/options. The linuxrc script is extended to search the boot command line for <drivername>.<option>=* strings for each driver loaded in initrd and add the <option>=* part to /etc/modprobe.d/options. 4. udev ------- Udev loads any modules which are not loaded by linuxrc scripts directly. It is possible to let udev load the required DRM and AGP modules provided it is made sure that this happens in the correct order. Since there is no explicit dependency of DRM modules to AGP drivers as there is no general one to one match between the two drivers a udev rule must exist to enforce the correct order for all cases where a AGP module is required. This is true for Intel DRM drivers and any other driver for an AGP graphics chip. For this a rule file 79-waitfor-agp.rules is added which is run before 80-drivers.rules. It checks if either an Intel graphics (class VGA) device is processed or if the graphics device is an AGP device. The latter condition is tested by an auxiliary tool (is_agp) which is passed the kernel name of the event device. If either condition is true udev will wait for /dev/agpgart to appear before proceeding to load a DRM driver module. 'is_agp' checks the capabilities flags in the PCI config space of this device for AGP. The changes to udev are not strictly required to make KMS work, still they augment the default module load process Installation ============ Modified packages for Factory of - kernel-source, - mkinitrd, - yast2-bootloader, - perl-Bootloader, - mkinitrd - udev can be found in my build service home on OBS under home:eeich:Factory-KMS. For installation add http://download.opensuse.org/repositories/home://eeich://Factory-KMS/openSU… to your installation repository and update the packages in question (going thru the usual vendor change hassle). It is advisable to update mkinitrd before updating the kernel. Then when the kernel is installed the modified mkinitrd will be used and all steps required to install KMS will be performed. TODO ==== - The kernel bootsplash sometimes produces wrong colors (WIP). Add KMS - Add KMS support to the RadeonHD driver. Cheers, Egbert. -- Egbert Eich (Res. & Dev.) SUSE LINUX Products GmbH X Window System Development Tel: +49 911-740 53 0 http://www.suse.de ----------------------------------------------------------------- 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

18 68

[opensuse-factory] [RFC] Drop glib/gtk/gnome 1.x stack
by Vincent Untz 11 Jan '10

11 Jan '10

Hi, For a while, I've been wondering why we still have glib 1.x and gtk 1.x (as well as some other part of the GNOME 1.x stack). So today I looked at this closely, and I think we can work towards removing those packages. Why should we remove those libraries? Well, they're not maintained upstream, and from a security point of view, this can be quite bad. See below for some analysis on which package it impacts, and what needs to be done. Please have a look at the list of packages that would get removed. Note: I've filed this as https://features.opensuse.org/308601 Thanks, Vincent ====================================================================== One package needs to be investigated: psx-plugins. All other packages fall in some category: Packages that need to be updated or changed =========================================== fvwm2-gtk: - this is only a GTK-based alternative for GUI elements in fvwm. Not critical. - remove the dependency from fvwm2 icewm: - simple wm - make it compile without imlib mgp: - tool for presentation - add patch to move to imlib2 (from Debian, and committed upstream) procmeter: - monitoring tool - version 3.5 is based on GTK+ 2.x qiv: - image viewer - version 2.2.2 (http://spiegl.de/qiv/) uses GDK 2.x smilutils: - tool to convert/edit digital video data (used by kino) - ported to GTK+ 2.0 in cvs - other distributions use code from cvs swami: - soundfont editor - uses GTK+ 2.x in svn - will have a release by next May according to mailing list TeX-Guy: - dvi library and utilities - GTK+ 1.x only needed for xgdvi - evince can replace xgdvi usbview: - display topography of USB devices - version 1.1 uses GTK+ 2.x WindowMaker-applets: - various applets for WindowMaker - it looks like E-Notes, wmtimer and wmcliphist are the ones requiring the new libraries - wmcliphist 1.0 uses GTK+ 2.x - wmtimer 2.92 uses GTK+ 2.x - e-notes 0.5 was released in 2001, and there has been no change since then (we have 0.4). Maybe just drop it? wmakerconf: - configuration tool for Window Maker - versions >= 2.11 use GTK+ 2.x xteddy: - some weird app ;-) - version 2.2 uses imlib 2 xzgv: - image viewer - 0.9.x versions use GTK+ 2.x Packages that can be safely removed =================================== ami: - Korean input method - scim deprecates this fnlib: - font rendering for enlightenment - was used by old versions of enlightenment only, as far as I know gau: - Gtk-based Hangul terminal emulator - shouldn't be needed with a recent terminal and a good Korean input method gdk-pixbuf: - library for images - can only be used with GTK+ 1.x (was integrated in GTK+ 2.x) gnome-libs: - GNOME 1.x libraries - can only be used with GTK+ 1.x goom2k4: - visual effects generator for mp3 players - not used by anything anymore, as far as I can tell (code was integrated in gstreamer) imlib: - image loading and rendering library - part of what we want to remove kanji-lookup: - simple kanji lookup application - gucharmap can be used nicolatter: - Japanese input method - scim deprecates this orbit: - GNOME 1.x library - can only be used with GTK+ 1.x Packages that can be removed, but with no replacement ===================================================== Those are all dead upstream. bombermaze: - game (bomberman/dynablaster clone) - similar games are available in the games OBS project (xblast, tomatoes) gbuffy: - mailbox watcher - patch to port to gtk2 available in case someone wants to resurrect the project: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515274 pcpmon: - graphical monitor for Performance Co-Pilot - kmchart is an alternative soundtracker: - sound editor - has been removed from Debian -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

16 42

[opensuse-factory] GRUB2 / FATE 308497
by Jeff Mahoney 06 Jan '10

06 Jan '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone - Occasionally I take a break from kernel hacking. Recently, I was working on improving the reiserfs support in grub so that it doesn't take forever to load when there is a journal with outstanding transactions that need to be replayed. The thing is that the grub 0.97 code is truly awful. Every file system implementation has to implement strangely chosen primitives and, outside of the code itself, has 32k in memory which it has to manage itself and not exceed. This is the crux of the reiserfs /boot performance issue in bnc#538795. On top of that, the upstream grub developers refuse to accept fixes or features against 0.97, forcing distributors to carry patches around forever. The good news is that GRUB2 lifts a whole lot of restrictions. It's modular in design, has a cleaner implementation, and has native support for more file systems. It supports LVM and MD RAID volumes. It supports DMRAID volumes (though I'm not sure how well here). The upstream development community is interested in maintaining it. The bad news is that it's a boot loader. There may be bugs lurking in there. That are tough to track down and leave you with an unbootable system. So who wants to help test? :) - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksee5UACgkQLPWxlyuTD7LfzgCeNNBHRMuyP8scWJrOfSjFkXiV fZkAoJoT9lBFwPxlzRRoA5UFjKzDMhUu =i06N -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

16 58

[opensuse-factory] Blender 2.49b
by Donn Washburn 02 Jan '10

02 Jan '10

In a konsole or from an icon Blender 2.49b fails to come up in KDE4 (kde4-4.3.85-1.1.i586) openSuSE 11.3, NVidia factory .run. Seems to be a KDE problem. Need a KDE BUG report? Compiled with Python version 2.6.2. Checking for installed Python... got it! ERROR: Unable to open Blender window As root or a user - it comes up and then disappears. -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 5

[opensuse-factory] KDE4<>KDE3
by Donn Washburn 31 Dec '09

31 Dec '09

Happy New Year to All; I just tried to get a audio mixer like kmix (Qt3) in openSuSE 11.3 using "zypper in kmix" Zypper came back with about 4 or 5 not needed thing that it was going to remove. Fine! Head on, Do it. Zypper started and removed about 25 packages and installed kmix. Execute kmix and <unknown program name>(829)/: KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." <unknown program name>(828)/: KUniqueApplication: Pipe closed unexpectedly. Kmix fails to work! Is there a list of QT4 <> QT3 programs like kmix to ? -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 10

Re: [opensuse-factory] [RFC] Drop glib/gtk/gnome 1.x stack
by Cristian Rodríguez 31 Dec '09

31 Dec '09

On 30/12/09 20:32, Philipp Thomas wrote: > On Wed, 30 Dec 2009 14:01:26 -0300, you wrote: > >> Yes, and looks like a suitable replacement for XMMS, Im actually using >> the RPM you just provided, thanks :) > > I will have to check in the next days as this sounds promising :) > >> Will be great If packman can ship a subpackage qmmp-restricted or >> similar though. > > I'll see what I can do as soon as I'm back from vacation. I already modified seife's package so it can be link'ed from packman OBS containing a "restricted" package wrapped in "if packman_bs.." We now need to a) package "ProjectM" libraries b) figure out if "bs2b" is patent encumbered. (legal folks ? ) c) test it, though it compiles with no warnings whatsoever. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] libxcb-shape.a
by Sid Boyce 29 Dec '09

29 Dec '09

xine-lib 1.1.17 calls for the above library which no longer is part of xorg-x11-libxcb-devel. There is just libxcb-shape.so.0.0.0 and its symlinks, also libxcb-shape.la which is used, it's still looking for the .a even with --enable-shared. I seem to remember that we were getting rid of .a libraries in openSUSE, the .a library was still hanging around unowned and unusable after up upgrades. I should think the problem is with the source code. Can anyone suggest a workaround - or may be the xine developers need to be made aware. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 7

[opensuse-factory] Christmas time
by Stephan Kulow 29 Dec '09

29 Dec '09

Hi, As many of us have vacation, there are currently not many commits - which is good as it gave me time to fix up the livecd build :) So for the first time since 11.2 we have building factory ISOS at: http://download.opensuse.org/factory/iso/ Happy vacation :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 9

[opensuse-factory] checkinstall
by Donn Washburn 29 Dec '09

29 Dec '09

openSuSE 11.2 RC 1 I see "checkinstall" is still broken. Something keeps it from writing in a directory that exist. /usr/src/packages/BUILDROOT -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 16

[opensuse-factory] Yast2 and USB Printers
by Donn Washburn 28 Dec '09

28 Dec '09

Hey Group; I have a USB Brother MFC 7840W and their custom driver for Linux. It was a RPM and downloaded from Brother's site for this printer, fax and scanner. I call up Yast2 (console or X) and the printer is found under Hardware. It seems to setup /etc/cups/ and printcap. Cups "d" is running according to "ps ax | grep cups" "lp file.text" seems returns a job number and lpq shows it. As for USB - lsusb and hwinfo --usb show it. Plus hwinfo --usb shows a kernel module that is seen with "lsmod" A website showed a way to test it using lptest and that worked for a test page. Where are what is causing it not to print? Sometimes it will wake up the display and says "Rec. Data" and then "Sleep". My guess is it is Brothers problem. Things like strace -fo stop at the end of cups from "lp file.txt" -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 5

[opensuse-factory] banshee
by Donn Washburn 27 Dec '09

27 Dec '09

Why is it that banshee causes www.pbs.org Frontline videos not to work? It must be broken like xine. Firefox calls banshee and nothing happens. -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] USB failure
by Donn Washburn 26 Dec '09

26 Dec '09

Hey Group; What is the reason that just about every new USB item seems to not work? I have a Palm Pilot that used to work flawless. I had a udev/rules.d file that setup a /dev/pilot which still works. The baud rate is the same and visor is shown by lsmod. Yet it doesn't work. I have a openSuSE rpm version of jpilot which will not sync. However just like my USB printer (said to work by linuxprinting.org) as well as the palm device - neither work. Anyone have a suggestion for tracking down the problem. -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- 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] Asterisk
by Hans Witvliet 25 Dec '09

25 Dec '09

Any chance of getting asterisk-1.6.2 on the obs? Like in: http://download.opensuse.org/repositories/network:/telephony:/asterisk/open… or http://download.opensuse.org/repositories/home:/vitsoft:/asterisk-dahdi/ope… hw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 5

[Fwd: Re: [opensuse-factory] Asterisk]
by Hans Witvliet 23 Dec '09

23 Dec '09

-------- Forwarded Message -------- > To: Hans Witvliet <hwit(a)a-domani.nl> > Cc: Marcus Meissner <meissner(a)suse.de>, opensuse-factory(a)opensuse.org > Subject: Re: [opensuse-factory] Asterisk > Date: Wed, 23 Dec 2009 00:09:12 +0100 > > On 2009-12-22 23:07:25 +0100, Hans Witvliet wrote: > > On Mon, 2009-12-21 at 23:44 +0100, Marcus Meissner wrote: > > > On Mon, Dec 21, 2009 at 11:29:28PM +0100, Hans Witvliet wrote: > > > > Any chance of getting asterisk-1.6.2 on the obs? > > > > > > > > Like in: > > > > http://download.opensuse.org/repositories/network:/telephony:/asterisk/open… > > > > or > > > > http://download.opensuse.org/repositories/home:/vitsoft:/asterisk-dahdi/ope… > > > > > > It is in OBS already, in network:telephony as you quote. > > > > > > It was removed from Factory due to the amounts of security updates it requires. > > > > > Was the removal before or after the official release of 1.6.2 ? > > I know that there were quite a number of release candidates, but since > > 18th of december the amount of updates should be minimal.... > Tnx Marcus (& vitsoft), for the speedy result. Noticed the 1.6.2 rpm's for both 11.0, 11.1, 11.2 and SLE_10 and SLE_11 Gesture is very much appreciated. Kind regards, Hans -- 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] Replacing -j%jobs with %_smp_mflags
by Jan Engelhardt 22 Dec '09

22 Dec '09

Hi, Most of SUSE specfiles include %{?jobs:-j%jobs} for parallel execution. It is also a well-known fact that quite some time is spent with setting up roots, etc., and compiling projects that can only do -j1. To keep the machine busy, I would increase the number of parallel build instances running. Furthermore, to not let parallel building go out of hand, I would switch from make -jX to make -lX. This would be straightforward to change in .rpmmacros (and/or build's equivalents, respectively): %_smp_mflags -l24 SUSE's specfiles however use a hardcoded %{?jobs:-j%jobs} (historic reasons?) which makes it impossible to easily change to other make flags. I could try touching the $MAKEFLAGS environment variable, but that may as well be reset, ignored, or whatever. In other words, I would prefer -l24 on the command-line. To that end, I am suggesting to change all %{?jobs:-j%jobs} found in specfiles by %_smp_mflags. It should be possible to do this in an automated fashion — projects which are not using -j%jobs in the first place (e.g. because they just are not capable) will not be affected anyway. N.B.: watch out for scons %{?jobs:--jobs=%jobs} which uses --jobs instead of -j. Thoughts? Jan -- 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] What happened to "xsnow"?
by Stefan Seyfried 22 Dec '09

22 Dec '09

Hi, where did the xsnow package go? It's still found on software.opensuse.org/search for FACTORY, but binaries can't be downloaded. It's also not in openSUSE:Dropped nor in home:hennevogel:todo Seriously, this is a bad time to leave users without xsnow! I'll bring my kids over to you to complain! ;-) I'd be willing to maintain this essential package. -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out." -- 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] Xorg taking 100% while dpms
by Per Osbäck 17 Dec '09

17 Dec '09

hi, anyone know anything about Xorg taking 100% during screen blanking/dpms? i am running KDE UNSTABLE at the moment, don't know if that could affect anything. regards, per -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 10

[opensuse-factory] Builds not against current perl 5.10.1
by Patrick Shanahan 17 Dec '09

17 Dec '09

I am currently unable to upgrade to perl-5.10.1 because current Factory builds of perl-spamassassin and apache2-mod_perl require perl-5.10.0. perl-5.10.0-72.5.x86_64 spamassassin-3.2.5-29.1.x86_64 perl-spamassassin-3.2.5-29.1.x86_64 apache2-mod_perl-2.0.4-40.92.x86_64 current yast2 requires perl-5.10.1 yast2-2.18.25-2.5.x86_64 yast2-core-2.18.19-2.3.x86_64 10:50 wahoo:~ > yast2 users Error loading language plugin /usr/lib64/YaST2/plugin/libpy2lang_perl.so: libperl.so: cannot open shared object file: No such file or directory Error while creating client module users My need for spamassassin is crippling my Factory system. Solution? tks, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

8 14

[opensuse-factory] cronie daemon is openSUSE
by Michal Seben 17 Dec '09

17 Dec '09

Hi SUSE folks ! Maybe you already know that vixie-cron is used as default cron in openSUSE. Currently there is no chance to push our ~20 patches to upstream (it's already dead), so my suggestion is : switch to cronie[1]. I prepared simple wiki[2] page about this step and also cronie package is waiting for testing in Base:System[3] repo. So if you want test cronie, just add Base:System repo (for opensuse 11.2) : zypper ar http://download.opensuse.org/repositories/Base:/System/openSUSE_11.2/Base:S… and install cronie (vixie-cron will be deleted): zypper in cronie Please let me know your opinions or suggestions :) [1] : https://fedorahosted.org/cronie/ [2] : http://en.opensuse.org/Cron_replace [3] : https://build.opensuse.org/package/show?package=cronie&project=Base%3ASyste… Thanks ! -- 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] The Future of SaX2
by Egbert Eich 17 Dec '09

17 Dec '09

The Future of SaX2 ================== For many years now SUSE Linux came with a tool to configure the setup of the desktop which was second to none in the Linux and Free Software world: SaX2. It made it easy even for unexperienced users to configure video modes, screen layouts as well as keyboard and input devices for the X Window System. Meanwhile however the technology around the X Window System server as shipped by X.Org has evolved: hot pluggable input and output devices made a static configuration infeasible. Automatic configuration and dynamic reconfiguration mechanisms have been developed such that today most of the tasks that SaX2 was able to do are done fully automatically on the fly and can be modified from within a desktop session. Modern desktops like Gnome and KDE provide convenient user interfaces for that. A static configuration of the Xserver as done by SaX2 is still possible, yet it does not work well together with dynamic reconfiguration. The changes to SaX2 to improve this situation would be considerable and will require substantial changes in its design. Novell has decided to no longer invest in development maintenance of SaX2 but instead rely on the new automatic and dynamic configuration features and invest in desktop applets to perform dynamic changes. Federico Quintero for instance has created gnome-display-properties. The resources needed to keep SaX2 in sync with changes in X.Org will exceed what the people at Novell who have been maintaining SaX2 next to their normal work tasks in the past few years are able to spare. Thus starting with openSUSE 11.2 SaX2 will no longer be offered as a configuration option in YaST. It is still shipped and installed by default but it's likely to be deprecated further when it's usefulness diminishes further. People have raised objections to this decision by Novell's as they believe a static configuration is still crucial while auto configuration is still new and still fails in a few cases where SaX2 successfully produces a usable configuration. Yet, the decision was driven by what Novell sees its business needs and thus is not up for discussion. However the fate of SaX2 is not at all up to Novell: SaX2 has been Free Software all along and as with all Free Software it's up to each individual to help driving it in the direction they like to see it go - independently of corporate business needs and interests. All it needs is a dedicated bunch - a group of people who still believe in it's value and who are willing to drive it further - or the corollary to this: if there is no such community it's most likely not considered useful enough to warrant the effort. Thus if you think a configuration tool for X like SaX2 is still what the world and you need, it is now time to act: Don't sit there and complain about a decision you cannot influence, pick up and start driving SaX2 development yourself - the sky's the limit! Don't be shy altering even fundamental basics of the SaX2 code basis - the configuration system in X has vastly changed, so a configuration tool needs to change the same way. The resources to do so are there: The project is hosted at: http://developer.berlios.de/projects/sax/ The openSUSE Devel project is at: https://build.opensuse.org/package/show?package=sax2&project=X11%3AUtilities Please join the developers mailing list at https://lists.berlios.de/mailman/listinfo/sax-devel If you are interested to contribute to SaX2. Cheers, Egbert. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

32 147

[opensuse-factory] Hardware enablement in kernel updates
by Jeff Mahoney 16 Dec '09

16 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - Some of you have seen my posts on this list before, but it may not be clear what my involvement is with kernel development. I lead one of the kernel teams in SUSE Labs. I maintain the master branch of the SUSE kernel trees (both SLE and openSUSE) and have been the release manager for the kernel for the past few openSUSE releases (as well as a few enterprise releases). Historically, some decisions have been made that affect the openSUSE kernel collaboratively, but not entirely transparently, and I'd like to change that. One of our policies regarding kernel updates is that we'll fix bugs pertaining to usability until the next release. Otherwise, it's security, data loss/corruption, and system crash fixes until EOL. While it could be argued that hardware enablement falls under usability, we haven't treated it that way in the past. I'd like to revisit that. I was asked today about the possibility of adding a driver to the 11.2 kernel, and I started thinking about it. Strictly speaking, it's against our inclusion policy. However, the new longer release cycle means that users with new hardware may be forced to run a Factory kernel on 11.2, switch to a different distribution, or wait around until the next release. While I don't personally have a problem with option #1, I'm a kernel hacker and kernel bugs don't scare me. Not everyone wants to be a beta tester. Option #2 isn't in the long-term interests of the openSUSE community. Option #3 is painful because it means that you have this shiny new hardware for which you've paid your hard-earned money and can't use to its fullest potential. The particular driver I was asked about is completely standalone. I don't have a problem including it since it won't affect anything else. The issue was that I don't want to encourage the expectation that this would be a normal occurrence - unless we want to change the policy surrounding updates. I should be clear on what I have in mind and what the limitations are. I do not intend to open the door for every crap driver that's floating around out there. There are reasons that the drivers aren't in the mainline kernel and I have no interest in duplicating that debate on this list. Drivers up for post-release inclusion _must_ be already in the mainline kernel. The other limitation is that the changes be completely standalone or isolated such that it's apparent that the introduction of the change doesn't affect the stability of users who are using those drivers already. That part can get sticky since adding a PCI ID is easy, but adding handling that is needed to enable that PCI ID while potentially affecting other devices in a clean way is not. So with that, I'd like to open it up for discussion. I've cross-posted between opensuse-factory and opensuse-kernel since it's a policy that affects everyone, not just those interested in the kernel itself. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksm4ecACgkQLPWxlyuTD7LD7QCeK9lDtJo6h/LcRnfng93+i0Pc Hv0An2Wnb1N41xxLSQjB830w1SwGdiUQ =Fwo1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

9 19

[opensuse-factory] RFC: Announcing important changes in the distribution
by Lubos Lunak 16 Dec '09

16 Dec '09

Hello, it repeatedly happens that there is a change introduced in the distribution that affects others yet those are not told at all or too late to do something about it. Examples would be the removal of X configuration including keyboard layout from YaST as a consequence of deprecating Sax2, meaning that it is now not possible to change keyboard layout for KDM/XDM, or the upgrade of PackageKit to a newer version that no longer had PolicyKit as a dependency but instead started requiring its newer and backwards incompatible version polkit-1, requiring rewritting KDE support from scratch (which is the reason why KDE in 11.2 uses polkit-gnome). In the first case, I don't remember that mentioned anywhere, in the latter case, the kupdateapplet maintainer was notified (where it didn't really matter) but not the KDE maintainers. Others could probably come up with their own examples. I'd prefer if such things didn't happen again, or at least if they were known in advance. And it even seems doable, because some changes already are announced, e.g. new gcc version, the switch to linking with --as-needed, etc. Therefore I want to suggest that announcing important changes in the distribution that affect other components of the distribution becomes mandatory. What would qualify for such a change is somewhat hard to specify exactly, but I'd hope using common sense to judge would do. For example "we remove support for X settings from YaST and require desktops to take care of these settings if necessary" or "we introduce new polkit-1, which is not backwards compatible to the old PolicyKit, and deprecate the old one" are clearly changes that should be announced. Something like "DHT support in KTorrent is now enabled/disabled" or "libjpeg is going to be upgraded from 6.2.0 to 6.2.1" is clearly of no interest, as long as it is not known to break other parts of the distribution - that would just create an unnecessary flood that nobody would follow. The place for such announcements would be this list, with some specific subject to make it easier to spot them (and perhaps some more firm pointing to the right list would be needed for those who create noise, or something from http://lists.opensuse.org/opensuse-factory/2009-09/msg00354.html would be needed). Comments? -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak(a)suse.cz , l.lunak(a)kde.org Lihovarska 1060/12 tel: +420 284 084 672 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

23 44

[opensuse-factory] repocache
by Hans Witvliet 16 Dec '09

16 Dec '09

Hi all, During my rsync i noticed the last couple of daay an increasing number files with the name "package.rpm-largehexnumber-number-number. For instance: ./KDE:/43/openSUSE_11.0/repocache/mono-kde4-4.3.4-3.7.i586.rpm-8f2ae283e855363e5ad51ce94f131fdc0f685273-597390-1260582155 As all of these files reside under a subdirectory "repocache" i wonder what its purpose is, And if it's none, why are they mirrored outside? I've been syncing 323229 of these files, while there are 156582 waiting to be downloaded. I don't mind burning cpu-cycles, or spending diskspace, but i rather like to know why..... Somehow i have a vague feeling that these are obs-internal-directories only, and not meant for the general public. Hans -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

Re: [opensuse-factory] New pm-utils-1.2.6.1
by Michal Vyskocil 15 Dec '09

15 Dec '09

On Tuesday 15 of December 2009 11:53:30 Stefan Quandt wrote: > > This release also removed powersave command. > > I'm using this all the time. > Will there be an alternative command? > I don't have such plans. But it'd be suitable to move it to the separate package (like powersave-legacy), which will be maintained by someone else. I offer a help with a packaging. BTW: in this case those two lines echo -e "ATTENTION:\tThis is a legacy tool to provide basic functionality of the obsolete" echo -e "\t\tpowersave daemon. It will vanish in future." should be removed from script ;-) Best regards Michal Vyskocil

2 2

[opensuse-factory] New pm-utils-1.2.6.1
by Michal Vyskocil 15 Dec '09

15 Dec '09

Hi all, I updated pm-utils to 1.2.6.1. The new version no longer supports HIBERNATE_METHOD={userspace,kernel} [1], because there's an upstream equivalent SLEEP_MODULE which selects one of available implementation (see /usr/lib/modules.d/ for details) # The default sleep/wake system to use. Valid values are: # kernel The built-in kernel suspend/resume support. # Use this if nothing else is supported on your system. # uswsusp If your system has support for the userspace # suspend programs (s2ram/s2disk/s2both), then use this. # tuxonice If your system has support for tuxonice, use this. # # The system defaults to "kernel" if this is commented out. SLEEP_MODULE="uswsusp" The SUSE default is uswsusp. This release also removed powersave command. BTW: development of suse addons to pm-utils is now on gitorious.org [2] [1] http://en.opensuse.org/Pm-utils#SUSE-specific_variables [2] http://gitorious.org/opensuse/pm-utils-suse Best regards Michal Vyskocil

1 0

Re: [Lxde-list] [opensuse-factory] submitreq #26939 and #26940 : xmms2 and LXMusic (LXDE Music player)
by Andrea Florio 14 Dec '09

14 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Il 14/12/2009 17:57, Jürgen Hötzel ha scritto: > 2009/12/11 Marcus Meissner <meissner(a)suse.de> > >> On Fri, Dec 11, 2009 at 02:27:09PM +0100, Marcus Meissner wrote: >>> On Fri, Dec 11, 2009 at 12:17:18PM +0100, Andrea Florio wrote: >>>> Hi guys, this two are my next LXDE submitreq. >>>> >>>> here some infos: >>>> >>>> (submit req #26940) >>>> (submit req #26939) >>> >>> I do not see either of them. >>> >>> There is 26240 though and 29239. >>> >>> Packaging wise I see no immediate issue with them. >> >> Except xmms2 seems to contain a MP3 decoder, which is not allowed >> in openSUSE. >> >> > MAD MP3 decoder plugin can be disabled at build time. > > Jürgen > that has been already done, and the source tarball has neem purged to have no more headers that includes problematic headers Andrea - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea(a)opensuse.org Packman Packaging Team Email: andrea(a)links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksmer0ACgkQyCZT87TFPuh49wCgmlo7sYCOLEOkMtatgfgNXxvl ytAAoMEiJ9HuS1XOVFnC/16j35YF/0cn =uxBS -----END PGP SIGNATURE----- -- 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] Security problem with mISDN?
by Joerg Mayer 14 Dec '09

14 Dec '09

Hello, I just stumbled on the following mail: http://www.isdn4linux.de/pipermail/isdn4linux/2009-December/004487.html As opensuse contains misdn here's my question: Is it possible for any user to dial any number in a system with default configuration? thanks Joerg -- Joerg Mayer <jmayer(a)loplof.de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. -- 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] http://en.opensuse.org/Roadmap
by Hans-Peter Holler 14 Dec '09

14 Dec '09

says: openSUSE 11.3 Schedule (preliminary) * Thu, Dec 12 openSUSE 11.3 Milestone 1 release seems this date is gone twice: December the 12# was yesterday (Saturday), last thursday was Dec 10. And yes I see "preliminary". Is there any news? Hans-Peter -- 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] Kernel oops 11.2
by Robert Schweikert 13 Dec '09

13 Dec '09

Does this have any meaning to anyone? This happens on openSUSE 11.2 (twice over the last 24 hours), when I was trying to load multiple web sites at the same time. One of the connections is trying to establish a VPN tunnel via SSL. Message from syslogd@triumph at Dec 12 06:06:06 ... kernel:[563299.498896] Oops: 0002 [#2] PREEMPT SMP Message from syslogd@triumph at Dec 12 06:06:06 ... kernel:[563299.498906] last sysfs file: /sys/devices/pci0000:00/0000:00:12.0/net/eth1/statistics/collisions Message from syslogd@triumph at Dec 12 06:06:06 ... kernel:[563299.499128] Stack: Message from syslogd@triumph at Dec 12 06:06:06 ... kernel:[563299.499128] Call Trace: Message from syslogd@triumph at Dec 12 06:06:06 ... kernel:[563299.499128] Code: df 4c 0f 45 f8 49 83 e7 df 4c 89 fa 4c 89 fb e8 fb fc ff ff 48 85 c0 74 31 48 8b 10 f7 c2 00 00 02 00 0f 85 59 02 00 00 48 89 c2 <f0> ff 42 08 f0 ff 40 0c f6 40 18 01 48 8d 55 c0 74 07 48 8b 95 Message from syslogd@triumph at Dec 12 06:06:06 ... kernel:[563299.499128] CR2: 0000000000000008 Linux triumph 2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 +0100 x86_64 x86_64 x86_64 GNU/Linux I am going to switch to the default kernel and see if that helps. There are two ethernet controllers on the machine. 00:11.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3) Subsystem: nVidia Corporation Device c73e Kernel driver in use: forcedeth 00:12.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a3) Subsystem: nVidia Corporation Device c73e Kernel driver in use: forcedeth Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Software Engineer Consultant LINUX rschweikert(a)novell.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 4

Re: [opensuse-factory] RFC: Announcing important changes in the distribution
by Robert Schweikert 12 Dec '09

12 Dec '09

Robert Schweikert Software Engineer Consultant rschweikert(a)novell.com 781-464-8147 Novell Making IT Work As One >>> Andreas Jaeger 12/10/09 9:52 AM >>> On Thursday 10 December 2009 15:03:45 Jano Kupec wrote: > On 12/10/2009 11:05 AM, Andreas Jaeger wrote: > > On Wednesday 02 December 2009 18:57:45 Lubos Lunak wrote: > >> [...] > >> The place for such announcements would be this list, with some specific > >> subject to make it easier to spot them (and perhaps some more firm > >> pointing to the right list would be needed for those who create noise, > >> or something from > >> http://lists.opensuse.org/opensuse-factory/2009-09/msg00354.html would > >> be needed). > > > > I see some consensus for this, so what tag should be used in the subject > > to mark it? Let's reword the proposal to work with missing details... > > > > I also suggest to have a factory development page that links to all these > > announcements, so that we reference them from one place. What do you > > think? > > What i don't like about the wiki is that it is hard to see incremental > changes to it, like you would see on a dedicated announce mailing list. > And you can reply to the announcement (in-lining the text) and further > discuss on opensuse-factory. > > I agree with Lars in the other mail, that we should use some exising > mailing lists, because we have too many, but opensuse-announce is for > user announcments, what we discuss here is more a developer thing. I > still see opensuse-factory for discussion (RFC or otherwise tagged > mails) and some dedicated list only for announcmements (low traffic, > only the results) as the best solution. > > But i'm also fine with just discussion on opensuse-factory and the wiki. > 'RFC' in the subject is fine for me. My proposal was to discuss on -factory and just have a pointer in the wiki to it so that somebody can easily lookup these some time later - so I think we're in agreement, Andreas I like the wiki and I like [ANNOUNCE] as a prefix. I still think we should have a more prominent place for this information on the main page (www.opensuse.org) With the wiki in place a link to the wiki page should suffice. I am mostly thinking of users not subscribed to any mailing list and people not necessarily in tune with checking the wiki for important information. Robert

6 9

[opensuse-factory] php5 question/issue/proposal ?
by Joop Boonen 11 Dec '09

11 Dec '09

Dear all, I'm building package php5-gtk because of the scan directory I have an issue when php5-gtk is installed in combination with apache2 i.e. for instance cacti doesn't work any more as php tries to start up with php-gtk when it's installed. I think it would be better to have outside of the /etc/php5/conf.d also /etc/php5/apache2/conf.d and /etc/php5/cli/conf.d in which specific ini files can be put that are only used for either apache2 or cli. In my case the php5-gtk.ini would reside in /etc/php5/cli/conf.d as it's a cli implementation only. I think the php5.spec file can be change in the following way: --with-config-file-scan-dir=%{php_sysconf}/conf.d %{php_sysconf}/$sapi/conf.d I've read that --with-config-file-scan-dir can now have more than one directory. Regards, Joop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 4

[opensuse-factory] submitreq 26278 - Package menu-cache (LXDE core dependency)
by Andrea Florio 11 Dec '09

11 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 going on with LXDE related submitrequests here some infos: bugowner : anubisg1 (me); the package is a core LXDE dependency, no bugs reported. The package is well test from various distros like fedora/mandriva/ubuntu and for example it's already into fedora and mandriva repositories. upstream project is [1] the upstream bugtracker is here: [2] and no security issue found yet (a review from security team maybe still be needed ) i want to maintain this package into Factory because i want to provide the full LXDE desktop enviroment and this package is one the components. see openfate feature [3] and bugzilla enhacement here [4] again, please consider that this is the most important BuildRequire for all LXDE enviroment License is GPLv2 Regards Andrea [1] http://lxde.org [2] http://sourceforge.net/tracker/?group_id=180858&atid=894869 [3] https://features.opensuse.org/307729 [4] https://bugzilla.novell.com/show_bug.cgi?id=561145 - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea(a)opensuse.org Packman Packaging Team Email: andrea(a)links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksin4kACgkQyCZT87TFPuiwHwCg5/R6XW4UPFFTA1HkvmUAnCQ+ b5EAnRqVSfBvYgIcUi0X7ngVLlEbim4u =rpLH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] [ANNOUNCE] ZYpp source repositories on gitorious.org/opensuse
by Duncan Mac-Vicar Prett 11 Dec '09

11 Dec '09

The ZYpp repositories previously published at git.opensuse.org repositories are now available on http://gitorious.org/opensuse http://gitorious.org/opensuse/sat-solver http://gitorious.org/opensuse/libzypp http://gitorious.org/opensuse/zypper http://gitorious.org/opensuse/zypp-utils (previously zypp/tools) http://gitorious.org/opensuse/libzypp-bindings http://gitorious.org/opensuse/libzypp-testsuite http://gitorious.org/opensuse/zypp-dialogsolver http://gitorious.org/opensuse/cmpi-zypp http://gitorious.org/opensuse/zypp-zmd-backend (previously zypp/backend) There is an initial opensuse-zypp team defined with access to those repositories. To switch you only need to edit your .git/config origin remote If before it was git@git.opensuse.org:projects/zypp/zypper.git Now it would be: git@gitorious.org:opensuse/zypper.git The repositories in git.opensuse.org are still accessible, but you can't push to them anymore. They will stay there until no repositories are left on that machine. Gitorious provides feeds for each repository pushes, and per each branch commits. To make it easier to follow the overall project, I have created this feed which merges various feeds and make the titles more similar to the old mails: http://pipes.yahoo.com/pipes/pipe.info?_id=36dc1dc1c0380cca92df9ddaa5b6e26d In the next days we will look for a solution to mail those feed updates to the commits mailing list. -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] submitreq #26939 and #26940 : xmms2 and LXMusic (LXDE Music player)
by Andrea Florio 11 Dec '09

11 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, this two are my next LXDE submitreq. here some infos: (submit req #26940) bugowner : anubisg1 (me); the package is here (X11:lxde) since about augoust, no bugs reported. The package is well test from various distros like fedora/mandriva/ubuntu and by me (almost daily use). upstream project is [1] the upstream bugtracker is here: [2] and no security issue found yet (a review from security team maybe still be needed ) i want to maintain this package into Factory because i want to provide the full LXDE desktop enviroment and this package is one the components. see openfate feature [3] and bugzilla enhacement here [4] Users will use it will be any LXDE user, and anyone needs a lightweight picture viewer License is GPLv2 please consider that his most important BuildRequire is provided by submitreq #26939 (submit req #26939) bugowner : anubisg1 (me); the package is here (X11:lxde) since long time, no bugs reported. The package is well tested maily by fedora and other distros that provides packages [5]. upstream project is [6] the upstream bugtracker is here: [7] and no security issue found yet (a review from security team maybe still be needed ) i want to maintain this package into Factory because i want to provide the full LXDE desktop enviroment and this package is one the components. see openfate feature [3] and bugzilla enhacement here [4] package use differet licenses for some plugins like LGPLv2+, GPLv2+ and BSD, all restricted modules has been disabled please consider that this is the most important BuildRequire for lxmusic submitreq #26240 Regards Andrea [1] http://lxde.org [2] http://sourceforge.net/tracker/?group_id=180858&atid=894869 [3] https://features.opensuse.org/307729 [4] https://bugzilla.novell.com/show_bug.cgi?id=561145 [5] http://wiki.xmms2.xmms.se/wiki/Download_XMMS2 [6] http://wiki.xmms2.xmms.s [7] http://bugs.xmms2.xmms.se/ - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea(a)opensuse.org Packman Packaging Team Email: andrea(a)links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksiKj4ACgkQyCZT87TFPug/kACcDP4xZdd1c1GTLLj7VZ50C4fo xbgAoKZbvatwlLBxffLGovJQ7O8SSBBr =TaMk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 8

[opensuse-factory] VLAN Config SLES11
by Günther J. Niederwimmer 11 Dec '09

11 Dec '09

Hello, can any tell me the way to configure vlan's for external on a SLES 11 System (my Server) On my system it is not possible to connect the router (5 IP's), I found nothing what is wrong in the logs? Is vlan not working on a SLES11 systems for external Network ? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- 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] usb printer tracking
by Donn Washburn 11 Dec '09

11 Dec '09

Hey Group; enclosed is an attempt to track out the reason my Brothers MFC7840W USB printer fails to work with openSuSE and Brothers free drivers. I see nothing in these errors that appears wrong. "lp", cups and libusb all seem to be working. The kernel module is mounted. I downloaded a standard Linux kernel and built it up even to try a different usblp kernel module - no help. http://localhost:631 amd Yast2 have been tried Can anyone suggest another idea to check - i have tried it as root and a user I have been tracking a error cusing a Brother's MFC7840W printer with Brother's -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316

1 0

[opensuse-factory] Changing alsa default sample rate
by Sid Boyce 10 Dec '09

10 Dec '09

My sound cards say they should be capable of 192K sample rate, but alsa seems to have a default of 48K. I tried the following in /etc/asound.conf, but it doesn't effect the change. I need it for alsa direct rather than for pulseaudio. # o /etc/asound.conf defaults.pcm.rate_converter "samplerate" Any clues? Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 12

[opensuse-factory] Fate #306591: entropy daemons in 11.2 - Kernel Removal IRQF_SAMPLE_RANDOM
by Rob OpenSuSE 10 Dec '09

10 Dec '09

I have taken an interest in Fate #306591 https://features.opensuse.org/306591 Andreas Jaeger has mused on community volunteer to package something. Now, I took a look at few suggestions, but 2 of them weren't "just work" in sense that they required webcam or mic, which seems like a possible can of worms to me. So I wondered about using timing jitter from user space? As a prototype I've knocked up short piece of C, which uses calls : nanosleep( &tsleep, 0); clock_gettime(CLOCK_REALTIME, &ttnow) This has been tested on i686 Athlon MP & P4 (Celeron Willamette) and x86_64 Athlon 64 x2; and I do appear to get a useful amount of unpredictable bits from this, even if the raw timings are not random. The timing jitter provides an externally unobservable measurement, and would allow sysadmin to tune to some extent eg) run 10 times/s (80bits/s) - 25 times/s (400bits/s). If this sounds like a useful approach, then I'd propose to continue on and develop a small daemon which gathers entropy bits from timing unpredictabilities caused by scheduler & interrupts, and also periodically gathers extra entropy (especially on startup) borrowing from techniques uses in the perl egd daemon (which would need modifying in any case). Obviously I'm a bit concerned about any move on power saving, this would obviously requires N wake ups, perhaps precautions would be needed to avoid them getting squeezed together by power saving patches which aim to batch up, code that sleeps like this? Rob -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 2

[opensuse-factory] [ANNOUNCE] Using the new accessibility stack in GNOME for Factory
by Vincent Untz 10 Dec '09

10 Dec '09

Hi, (please follow-up on opensuse-gnome, unless you have a cross-desktop point) People have been working on a new accessibility stack based on dbus for the past few months, and even though we had preliminary packages in 11.2, it was not really ready for real-world testing. We're reaching this point today. I opened a feature [1] to track this. The goal of doing this change now is to test this new stack, and help us decide if we want to use it in 11.3, or not. This should also help upstream find and fix bugs in the new stack. But for this to really work, we need help from people. How can I help? =============== If you know accessibility, you can certainly help. You'll need factory (or a development version of 11.3), and you'll need to make sure the new stack is installed. And then, just try some accessibility features to see what works, what doesn't work, etc. If you don't know accessibility, just join the GNOME accessibility effort: people will help you start. They have a good wiki page [2] that is the first place you should look. How can I have the new stack? ============================= Make sure at-spi2-core is installed. If you have gtk2, you should automatically get at-spi2-atk too. That's all. You're done. How can I switch to the old stack? ================================== Both stacks are parallel-installable. To use the old stack, you simply need the at-spi package, and you should set the /desktop/gnome/interface/at-spi-corba gconf key to true. While the two stacks are parallel-installable, I'm unsure that using the old one when the new one is installed works (it should, but there might be bugs). If this is the case, you can remove the old stack. But please file a bug too. Why a new stack? ================ The rewrite of the stack was triggered by technical reasons (moving away from corba to dbus). So the goal is not to propose new features, or to remove anything. But there'll probably be regressions. This rewrite should also help KDE share the same infrastructure; I think this is still something being worked on, though (someone else might be better informed). What changes? ============= For people not using accessibility, nothing should change. For people using accessibility: - you should be able to use orca and accerciser in the very same way - I believe the magnifier and the on-screen keyboard will not work fine (gnome-mag and gok). I'm actually not sure we can make them work with the new stack, so maybe we'll have to switch back because of this - accessibility of bonobo objects (that's mainly panel applets at this point) will likely be broken. Vincent [1] https://features.opensuse.org/308451 [2] http://live.gnome.org/Accessibility -- Les gens heureux ne sont pas pressés. -- 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] updated firmware v3.1 for ipw2200
by Stefan Seyfried 10 Dec '09

10 Dec '09

Hi, I updated the ipw-firmware package to contain the version 3.1 for ipw2200. There is no changelog for the firmware version (even the Intel guys could not get one when they announced this version in March), but the driver developers generally recommend to use the latest firmware. So I'd ask everyone using an intel 2200bg or 2945abg module to watch out if it changes anything to the worse for them once my submitrequest is accepted and goes into FACTORY. If we find out that the newer version causes regression, we might need to find a way of installing both and selecting one of them, but I would really like to avoid that. Have fun ;) seife -- Stefan Seyfried "A lonely little useless module - no-one needs it, and it needs no-one else either. How sad." -- okir -- 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-packaging] New osc 0.124 release
by Stefan Seyfried 10 Dec '09

10 Dec '09

Hi Adrian, 2009/12/10 Adrian Schröter <adrian(a)suse.de>: > > Hello, > > we put out the new osc version 0.124 release in the openSUSE:Tools project. could you please submitrequest it to Factory? Thanks! seife -- 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] DirectFB compat package
by Stefan Seyfried 09 Dec '09

09 Dec '09

Hi, For those running FACTORY on a machine having installed a particular M(edia)Player from packman, there is a problem since the 10.2 version there needs DirectFB < 1.2.9, but FACTORY now has 1.2.9 So to fix that, you can install DirectFB-compat-120 (i named it after the library version) from http://download.opensuse.org/repositories/home://seife://testing/openSUSE_F… Note that I had to rpm -e --nodeps DirectFB rpm -hiv DirectFB-compat-120.*.rpm (probably because of not-perfect provides/obsoletes/whatever), but you hopefully only will need to do this once in this FACTORY cycle. Then I could do zypper up and get everything that did not get installed before (DirectFB-1.2.9, splashy, ....) because it would have broken MPlayer. Hope that helps someone. Oh - and I do *not* recommend anyone to add home:seife:testing as a regular repository ;) Have fun, seife -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out." "Praktische Erfahrung ist viel Wert. Nur mal davon gehört zu haben, daß etwas nicht funktioniert, ist eine Sache - den GNOME Dateidialog selbst benutzt haben zu müssen, eine ganz andere." -- Steffen Winterfeldt I don't know why I dream this way The sky is purple and things are right every day I don't know, it's just this world's so far away But I won't fight, and I won't hate / Well not today "I personally just encourage people to switch to KDE. This 'users are idiots, and are confused by functionality' mentality of Gnome is a disease. [...]. Please, just tell people to use KDE." -- Linus Torvalds "[...] a 'enterprise desktop' should never be allowed to drive development. It is, by definition, boring and same-old, same-old." -- Linus Torvalds "You sure you software suspend guys haven't been hanging out with the IDE maintainers?" -- Rob Landley Never trust a computer you can't lift. You are storing 40 billion bits of information on a lump of metal and glass rotating at 10,000rpm and pushing into areas of quantum theory in order to store you data. It should be no suprise it might not be there a month later. -- Alan Cox "A lonely little useless module - no-one needs it, and it needs no-one else either. How sad." -- okir "Data security manager [...] presents new company security policy. It reads like a help text for a tax declaration" -- draht "I've never seen this before." "Its a blue light." "What does it do?" "Turns blue." "Mit Außerirdischen, die nicht weiter gekommen sind als Microsoft und Apple, will ich persönlich nichts zu tun haben." -- Prof. Harald Lesch -- 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] submitreq 26096 - Package GPicView (LXDE photo viewer)
by Andrea Florio 09 Dec '09

09 Dec '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, i'm beginning to submit the first LXDE packages to factory. here some infos: bugowner : anubisg1 (me); the package is here (X11:lxde) since about 6 months yet, no bugs reported. The package is well test from various distros like fedora/mandriva/ubuntu and by me (daily use). upstream project is [1] the upstream bugtracker is here: [2] and no security issue found yet (a review from security team maybe still be needed ) i want to maintain this package into Factory because i want to provide the full LXDE desktop enviroment and this package is one the components. see openfate feature [3] and bugzilla enhacement here [4] Users will use it will be any LXDE user, and anyone needs a lightweight picture viewer License is GPLv2 Regards Andrea [1] http://lxde.org [2] http://sourceforge.net/tracker/?group_id=180858&atid=894869 [3] https://features.opensuse.org/307729 [4] https://bugzilla.novell.com/show_bug.cgi?id=561145 - -- - ------------------------------------------ Andrea Florio QSI International School of Brindisi Sys Admin openSUSE-Education Administrator openSUSE Official Member (anubisg1) Email: andrea(a)opensuse.org Packman Packaging Team Email: andrea(a)links2linux.de Web: http://packman.links2linux.org/ Cell: +39-328-7365667 - ------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksfe0kACgkQyCZT87TFPug3lwCeN0kgJbIIVwK3Oq/9CB9k8MeD UigAniXWd3UnPHNRWB27gtCAec10PfMT =9la5 -----END PGP SIGNATURE----- -- 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] Product Creator image problems on system with multiple CD/DVD drives
by Jeromy Smith 08 Dec '09

08 Dec '09

I have created an image using Product Creator on openSUSE 11.2 that has a couple of add on sources (oss, non-oss, updates, nvidia). On a system with a single DVD drive, the installation completes successfully and in a timely manner. On a system with two drives, the installation takes a considerably longer time to complete. If I look at /var/log/YaST2/y2log, I can see that it is trying to mount the second drive continually throughout the install process. Is this behavior expected? Are there any install options that can make it ignore the second drive? Thanks, Jeromy -- 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] Should touchpad padding be disabled by default?
by Hans-Peter Holler 08 Dec '09

08 Dec '09

Hi, see https://bugzilla.novell.com/show_bug.cgi?id=554884 _My_ solution for kde4: ~/.kde4/Autostart/touchpad.sh: synclient TapButton1=1 Hans-Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 7

[opensuse-factory] dropping BitTorrent (Mainline) package
by Jan Matejek 08 Dec '09

08 Dec '09

dear openSUSErs, for a long time we've been distributing the official BitTorrent (a.k.a. Mainline) client. And for some years we've been stuck with version 4.0.4, because we couldn't include DHT support (legal reasons). Now that it turns out that we can include DHT after all, it also turns out that mainline's source is closed since 2007 or something. There is still version 5.3 available under GPL, but i don't see much value in upgrading to version that is three years old. (and to be perfectly honest, i'm not even sure that our BitTorrent version still works) We now have better bittorrent clients for GUI (KTorrent, Transmission) as well as for console (rtorrent - not in the official distro, but can be found in OBS), so losing Mainline shouldn't be a problem. If you use bittorrent in headless environments, you might be interested in combining ncurses-based rtorrent with 'screen'. Deleterequest#25604 filed. May you rest in peace, BitTorrent. regards m. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

8 18

[opensuse-factory] a KTTSD error
by Donn Washburn 08 Dec '09

08 Dec '09

Hey Group; I am getting after last nights "zypper up" and KDE error. "Starting KTTSD Failed" -- 73 de Donn Washburn 307 Savoy Street Email:" n5xwb(a)comcast.net " Sugar Land, TX 77478 LL# 1.281.242.3256 Ham Callsign N5XWB HAMs : " n5xwb(a)arrl.net " VoIP via Gizmo: bmw_87kbike / via Skype: n5xwbg BMW MOA #: 4146 - Ambassador " http://counter.li.org " #279316 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 6

[opensuse-factory] yast backup tmp files
by jdd 07 Dec '09

07 Dec '09

Hello, I notice that yast, option "backup" still uses /tmp as temporary place. Giving this backup can be very hudge, how is it possible to use an other place? is that worth a bugzilla? thanks jdd -- http://www.dodin.net http://valerie.dodin.org http://news.opensuse.org/2009/04/13/people-of-opensuse-jean-daniel-dodin/ -- 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] opensuse source?
by Rob OpenSuSE 07 Dec '09

07 Dec '09

Am including Factory list, perhaps in 11.3 a better way of making source available to end users, which avoids big load on Build Service and Mirrors is possible? On project list, a request was made for source by someone unfamiliar with openSUSE suggested an ISO; installing source rpm's with YaST is not working as it did in past for me, because only binary packages are held on most of the download.opensuse.org mirrors. 2009/12/4 Peter Pöml <poeml(a)cmdline.net>: > Am 04.12.2009 um 09:56 schrieb Karsten König: > >>> All of that is not doable via offering source rpms, so, maybe we can get >>> rid of src rpms at all later ... >> >> Currently osc/obs webfrontend is for novell accounts only, and also a >> seperate >> tool if one wants to really see the history of the package (osc) > > I agree, that's really bad. > >> So the srpms fill an important niche, people from upstream projects >> getting >> bugreports can simply go ahead, download the source rpm and check the >> .spec >> file for obvious mistakes in the building process and/or check the patches >> applied. >> >> Before dumping source rpms for saving space, which is somewhat >> questionable >> looking at the huge space and traffic the home: repositories generate, >> people >> need an anonymous read access, I don't think any other distribution forces >> something like this on external people. > > Source RPMs have a special drawback in the build service: they are published > as many times as there are build targets, with slight variations only. See > http://lists.opensuse.org/opensuse-buildservice/2009-06/msg00169.html > > Well, that's were 30-50% of the build service disk space goes! > > This is a similar percentage of space as the home: namespace. It is > significant :-) > > Excluding build service source RPMs from mirroring is an important > instrument to find fmirrors at all. So problems are : 1) source rpm's are changed and re-published over frequently by Build service 2) source rpm take huge diskspace and bandwidth, for something rarely required on installed system 3) obtaining the source to build and modify a package on end-user system (as required by GPL) is less obvious than it was in past Can we simply have seperate hosts in URI's for binary download, binary debug & source packages? What about a way to install all the source of used packages? Obtaining all the project source is handled by snail mail request for a (possibly chargeable) DVD. Rob -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

8 16