September 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Incompatible diff format?
by Ilya Chernykh 24 Sep '11

24 Sep '11

I have a diff with the following heads, exported from the SVN: -------------------------- |Index: cisreg.h |=================================================================== |--- cisreg.h (.../trunk/KDE/kdeutils/klaptopdaemon/linux) (revision 409203) |+++ cisreg.h (.../branches/trinity/kdeutils/klaptopdaemon/linux) (revision 1254856) -------------------------- How can I apply such patch? I get an error. -- 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] Re: [opensuse-project] Re: [opensuse-arm] Growing some openSUSE ARMs
by Joop Boonen 23 Sep '11

23 Sep '11

On Fri, September 23, 2011 9:16 pm, Jan-Simon Möller wrote: > <snip> > Well cool - why did it take us ~ 1.5 years to notice ;) . > I just dropped factory pack then as it is too much for just one penguin. >> > 2) SUSE are going to be doing another HackWeek (I think it is next >> week) >> > which means Adrian, Alex, Dirk and anyone else that has knowledge, experience or interest can join in the fun and pain almost full time >> for >> > a week - let's not kid ourselves here there is a high probability for lots of pain, but also fun ;-) Thing is HackWeek is not just for SUSE staff, it is also for the community. You can join in and spend some quality time on the project with those that know a whole heap of >> stuff, >> > and learn from them and maybe even teach them something too. >> > We are going to be targeting ARMv7 nothing older I'm afraid this means >> > CORTEX-A8 and above (looking at A9 primarily and then the new A15 when >> > it's available), it gets too messy otherwise and it is already messy enough.If you have knowledge and experience, please help out. If you don't take part you have no justification to complain - you've got to >> be >> > in it to win it ;-) >> > So I'm basically just giving you all a heads up on this effort, and >> will >> > update you as regularly as possible (I'm hoping to do something weekly >> > maybe). In the meantime, if you're interested join #opensuse-arm on Freenode and the opensuse-arm mailing list. *DO NOT HARRASS* for updates, if there is something to say it will be said. If you've got a >> > question, ask and *WAIT* for an answer. If you want to help out but >> want >> > to know how ask and *WAIT* for an answer. I will try and get something >> > on the wiki soon, with a todo list etc. >> I think we should get people like Jan-Simon Möller on board as he started >> the first openSuSE ARM build in 2009 and also the ARM build in OBS. I think it'll kick-start the ARM port. >> > Thanks and here's to getting our Geeko some ARMs. > So let get a crew together - we have the knowledge and the tools. I'm willing to do my part on the weekends and continue what I did back then. > Time to wipe android from the transformer ?! ;) That'll be one mean machine. (Certainly the upcoming Transformer 2 (TF201 ?) with the Tegra Kal El) I have looked into the Tegra2. I've read this story in connection with hardfp. http://www.slashgear.com/meego-tegra-2-drivers-could-end-android-monopoly-o… http://www.meegoexperts.com/2011/07/nvidia-meego-battle-ground/ This looks quite promising. I don't know when these drivers will be available I couldn't find any information yet. > Best, > Jan-Simon Just some information as people are looking into hardware. The trimslice might also be an option as you'll get 45% off as a developer, I don't know if it's still valid. http://trimslice.com/web/dev-kit IMHO the advantage it that there are a lot of Tegra devices Tablets etc. The disadvantage is IMHO that the driver is closed source. I don't know if the nouveau project could change this? Regards, Joop. -- 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] To people who run Factory
by Ilya Chernykh 23 Sep '11

23 Sep '11

Can you please check if KDE3 works well in Factory? I received some reports that it does not work well and some applications are unstable. Since I do not run Factory, I cannot check it myself. -- 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] consolidating the list of mysql flavors in Factory
by Dirk Müller 23 Sep '11

23 Sep '11

Hi, at the moment we seem to have the following mysql flavors in Factory: mysql-community-server mysql-cluster mariadb There might be more that I don't know about. Given that mysql is a package that needs frequent updating (both for security and for non-security bugfix reasons); I was wondering if it really makes sense to have multiple flavors of it in Factory (and thereby in openSUSE 12.1). We did so in the past for 11.3 and 11.4, and noticed that this was a problem (security updates took look to be submitted, and then they had major regressions that broke severly). So, my question is twofold: - is there anyone stepping up to maintain mariadb and mysql-cluster for the full openSUSE lifetime? - if no, who would object (and why) to dropping those variants from factory? Note that the other flavors can still be in server:database, even built for older distros, so those who really want it can use it. Thanks, Dirk -- 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] Are precompiled jar files allowed in packages?
by Kirill Kirillov 23 Sep '11

23 Sep '11

Hi! mucommander package was rejected due to precompiled jar files: https://build.opensuse.org/request/show/82152 But I see packages in the Factory with precompiled jar files, e.g.: https://build.opensuse.org/package/show?package=tuxguitar&project=openSUSE%… Could you please clarify this? Thanks! -- Kirill Kirillov <>< -- 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-arm] Re: [opensuse-factory] Growing some openSUSE ARMs
by Joop Boonen 23 Sep '11

23 Sep '11

On Thu, September 22, 2011 4:42 pm, Markus Slopianka wrote: > On Donnerstag 22 September 2011 16:05:44 Andrew Wafaa wrote: > >> the architecture that powers most of your little devices (and some bigger ones too). Almost all smartphones, tablets and many other consumer devices are powered by ARM from one of the numerous licensees. > > The openSUSE member who were allowed to vote decided that openSUSE does not want to run on > those âlittle devicesâ. http://en.opensuse.org/openSUSE:Strategy says: >> openSUSE does not: >> (...) >> Work on Mobile or embedded devices. See also link: http://news.opensuse.org/2011/08/09/strategy-done/ <quote> The future The team noted that the strategy is of course not set in stone for eternity although we probably wont go through this process every year and asked for further feedback in the mass mailing to the membership. Some comments did indeed come in, most notably asking for the ARM port and mobile devices as well as the impact of the openSUSE Foundation. In the future, the strategy documents will surely require some revision. Once somebody in the openSUSE community steps up to do an ARM port, which is likely to attract significant help, the document will have to be revisited to reflect this, just like Tumbleweed resulted in a change. </quote> Joop -- 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] lightdm-branding-openSUSE review
by Guido Berhoerster 23 Sep '11

23 Sep '11

Hi, my sr of X11:xfce/lightdm-branding-openSUSE to Factory has been rejected on the grounds that it doesn't provide a copy of the GPL (see bnc#716059) although in fact it does include a copy from the main lightdm package. I haven't been able to get any response from the legal team either through bugzilla or via mail, could somebody please comment on this? I need to get this into Factory ASAP. Thanks, -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 3

[opensuse-factory] A package fails when building against current Factory
by Ilya Chernykh 23 Sep '11

23 Sep '11

Hi! I receive the following error message: -------------------------------------------------------------------- package: arts SuSEconfig.permissions modified files that are not properly handled! this will break rpm -V, ask ro for details. diff for both runs of rpm -V: +/opt/kde3/bin/artswrapper should be root:root 4755. (wrong permissions 0755) -------------------------------------------------------------------- I actually do not understand what it wants. I tried to change permissions of /opt/kde3/bin/artswrapper to 4755 but this did not help. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 4

Re: [opensuse-factory] Running Qt applications as root bug, not present in XFCE
by Steven Sroka 22 Sep '11

22 Sep '11

On 22 September 2011 17:30, Steven Sroka <sroka.steven(a)gmail.com> wrote: >>On 21 September 2011 17:43, Roger Luedecke <roger.luedecke(a)gmail.com> wrote: >> Running Qt applications as root bug, not present in XFCE. It uses the >> correct widget set and colors. Looks to me like we can fix the bug by seeing >> how YaST gets its setting info from XFCE and comparing what is different >> between it and KDE. Are you referencing KDE bug#277249? >> -- >> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org >> For additional commands, e-mail: opensuse-factory+help(a)opensuse.org >> >> > -- 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] Kernel for 11.4?
by Jeff Mahoney 22 Sep '11

22 Sep '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - Since technically we're in feature freeze for 11.4, I thought I'd put this out for discussion. Factory is currently using 2.6.36 which was released 3 weeks ago. Upstream versions tend to take about 10-11 weeks, on average, to release. The scheduled release for the first openSUSE RC is Jan 20. The scheduled release for the first RC is Jan 20. The typical development time for a kernel release, on average, is about 10-11 weeks. That puts the release of 2.6.37 around Dec 29 to Jan 12. That sounds like kind of a tight window, but the reality is that the differences in the later kernel RCs tend to be small and fix bugs. The "real" development happens in -rc1, which was released about two weeks ago. Later -rcs serve to stabilize the development that went into -rc1. So, the the feature freeze aspect of it will be a one-shot, when I update to -rc1. (Actually, I hardly ever update to -rc1 and instead use - -rc2 which tends to be more stable). I've already done the merge work for 2.6.37-rc1 since the master kernel always tracks the latest upstream. Xen is the lone exception, as it usually is, but Jan Beulich has been great about getting that completed shortly after I do the update. This time might be a little more difficult because much of the Xen code has been merged into the mainline kernel so there's some sorting out to be done. As far as testing goes, we're still early enough that we won't lose a lot of effort. I'd update Factory to 2.6.37-rc2 as soon as it is released upstream, which should be this week. Our usual corps of dedicated testers can dig in quickly. In my experience, though, the number of testers drastically increases around the RC1 release. I wish it weren't so, but it is. So revving the kernel now isn't likely to toss out a lot of testing. The biggest "feature" I'm going for is not having to backport fixes from 2.6.37. The BKL removal patches and the VFS scalability patches are going to improve performance on multicore systems. The removal of I/O barriers should also be pretty noticeable but I haven't had time to verify that yet. So, opinions? - -Jeff Features that are going into 2.6.37: - - The inode portion of the VFS scalability patches - - More BKL removal, including parts of the core kernel - - Block I/O can be throttled via cgroups - - Simple pNFS support - - In-kernel PPTP (tunneling) acceleration - - "Lazy" inode table creation for ext4 to allow faster fs creation - - Batched discard support, which allows the file system to advise the block layer to use the TRIM command. This allows online TRIMs, but is only implemented in ext4 so far. - - Xen dom0 support (mostly) - - The usual round of bug fixes. - - fanotify - - Block barriers have been removed[1] Drivers: - - Systems and processors: - Flexibility Connect boards - Telechips TCC ARM926-based systems - Telechips TCC8000-SDK development kits - Vista Silicon Visstrim_m10 i.MX27-based boards - LaCie d2 Network v2 NAS boards - Qualcomm MSM8x60 RUMI3 emulators - Qualcomm MSM8x60 SURF eval boards - Eukrea CPUIMX51SD modules - Freescale MPC8308 P1M boards - APM APM821xx evaluation boards - Ito SH-2007 reference boards - IBM "SMI-free" realtime BIOS's - MityDSP-L138 and MityDSP-1808 systems - OMAP3 Logic 3530 LV SOM boards - OMAP3 IGEP modules - taskit Stamp9G20 CPU modules - aESOP Samsung S5PV210-based Torbreck boards - - Block: - Chelsio T4 iSCSI offload engines - Cypress Astoria USB SD host controllers - Marvell PXA168/PXA910/MMP2 SD host controllers - ST Microelectronics Flexible Static Memory Controllers - - Input: - Roccat Pyra gaming mice - UC-Logic WP4030U, WP5540U and WP8060U tablets - several varieties of Waltop tablets - OMAP4 keyboard controllers - NXP Semiconductor LPC32XX touchscreen controllers - Hanwang Art Master III tablets - ST-Ericsson Nomadik SKE keyboards - ROHM BU21013 touch panel controllers - TI TNETV107X touchscreens - - Miscellaneous: - Freescale eSPI controllers - Topcliff platform controllher hub devices - OMAP AES crypto accelerators - NXP PCA9541 I2C master selectors - Intel Clarksboro memory controller hubs - OMAP 2-4 onboard serial ports - GPIO-controlled fans - Linear Technology LTC4261 Negative Voltage Hot Swap Controller I2C interfaces - TI BQ20Z75 gas gauge ICs - OMAP TWL4030 BCI chargers - ROHM ROHM BH1770GLC and OSRAM SFH7770 combined ALS and proximity sensors - Avago APDS990X combined ALS and proximity sensors - Intersil ISL29020 ambient light sensors - Medfield Avago APDS9802 ALS sensor modules - Basic, memory-mapped GPIO controllers - Intel Topcliff GPIO controllers - Intel Moorestown/Medfield i2c controllers - IDT CPS Gen.2 SRIO RapidIO switches - Freescale i.MX DMA engines - ARM PrimeCell PL080 or PL081 DMA engines - Cypress West Bridge Astoria controllers - USB ENE card readers - Asahi Kasei AK8975 3-axis magnetometers - OLPC XO display controller devices - Analog Devices AD799x analog/digital converters - Winbond/Nuvoton W83795G/ADG hardware monitoring chips - Flarion OFDM usb and pcmcia modems - Maxim MAX8952 and MAX8998 Power Management ICs - National Semiconductors LP3972 PMIC regulators - Broadcom BCM63xx hardware watchdogs - - Network: - Brocade 1010/1020 10Gb Ethernet cards - Conexant CX82310 USB ethernet ports - Atheros AR9170 "otus" 802.11n USB devices - Topcliff PCH Gigabit Ethernet controllers - Intel Topcliff platform controller hub CAN interfaces - Technologic Systems TS-CAN1 PC104 peripheral boards - SBE wanPMC-2T3E3 interfaces - RealTek RTL8712U (RTL8192SU) Wireless LAN NICs (replaces older rtl8712 driver) - Atheros AR6003 wireless interface controllers - Beeceem USB Wimax adapters - Broadcom bcm43xx wireless chipsets - - Sound: - Marvell 88pm860x codecs - TI WL1273 FM radio codecs - HP iPAQ RX1950 audio devices - Native Instruments Traktor Kontrol S4 audio devices - Aztech Sound Galaxy AZT1605 and AZT2316 ISA sound cards - Wolfson Micro WM8985 and WM8962 codecs - Wolfson Micro WM8804 S/PDIF transceivers - Samsung S/PDIF controllers - Cirrus Logic EP93xx AC97 controllers - Intel MID SST DSP devices - - USB: Intel Langwell USB OTG transceivers - YUREX "leg shake" sensors - USB-attached SCSI devices - - Video4Linux2: remotes using the RC-5 (streamzap) protocol - Konica chipset-based cameras - Sharp IX2505V silicon tuners - LME2510 DM04/QQBOX USB DVB-S boxes - Samsung s5h1432 demodulators - Several new Conexant cx23417-based boards - Nuvoton w836x7hg consumer infrared transceivers - OmniVision OV6650 sensors - OMAP1 camera interfaces - Siliconfile SR030PC30 VGA cameras - Sony imx074 sensors - VIA integrated chipset camera controllers - -Jeff [1] This is because they were a very big hammer that had a reputation for killing performance. They're necessary for safely using journals on devices with write caching enabled, but were implemented by flushing the entire I/O queue to physical media -- not just "to disk" which includes the disk's write cache. The new implementation will still use the flush-to-media feature but will not stall the i/o queue. - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkzhW0YACgkQLPWxlyuTD7JgBACbBfR+uJwfKKnEcBZIg/KeIj/S hikAnRiL9nG50QoKZkrn1AsmGljnGvYn =T/Hp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

15 33

[opensuse-factory] KDE3 Pattern...
by Kim Leyendecker 22 Sep '11

22 Sep '11

Am 21.09.2011 18:20, schrieb Ilya Chernykh: > On Wednesday 21 September 2011 20:18:05 Kim Leyendecker wrote: > >>>>> > >> > I don't want another KDE pattern. This is very confusing for users. >>> > > How about building KDE3 appliance in SUSE Studio then? I think there is >>> > > a template only if there is a pattern. >>> > > >> > >> > What about them then? > They are built package by package, but it is quite difficult to create a new appliance not fitting > into suggested templates. If you create an appliance, it suggests Gnome, KDE4, minimal X etc. > For 10.3 it also suggests KDE3. First: I created a new thread to not hijack coolo´s show stopper thread anymore. Second: Why you don´t use a 10.3 with KDE3 and update it to the latest openSUSE release. I will search a 10.3 image and try it. kind regards, -- -o) Kim Leyendecker /\\ openSUSE Ambassador, openSUSE Wiki Team DE _\_v http://www.opensuse.org - Linux for open minds -- 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] python-ipaddr
by Claudio Freire 22 Sep '11

22 Sep '11

I've been preparing a package of python-ipaddr in OBS[0] The library is a dependency of another project I'm trying to package, and since it's a general enough library I thought I might submit it. It's very useful when working extensively with IP addresses, since it provides lots of stuff python's stdlib doesn't. I tried to follow all the guidelines for python packaging, I tried the package in my own 11.4 and it works Ok. The only thing that makes me doubt is the requirement for a CLA[1] in order to submit patches upstream. How does the community deal with this? If the CLA is no issue, I'll try to submit the package to factory before the next milestone. [0] https://build.opensuse.org/package/show?package=python-ipaddr&project=devel… [1] http://code.google.com/p/ipaddr-py/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 4

[opensuse-factory] Re: [opensuse-arm] Re: Growing some openSUSE ARMs
by Joop Boonen 22 Sep '11

22 Sep '11

On Thu, September 22, 2011 5:41 pm, Guillaume Gardet wrote: > > > Le 22/09/2011 16:56, Greg KH a écrit : >> On Thu, Sep 22, 2011 at 03:05:44PM +0100, Andrew Wafaa wrote: >>> We are going to be targeting ARMv7 nothing older I'm afraid this means CORTEX-A8 and above (looking at A9 primarily and then the new A15 when it's available), it gets too messy otherwise and it is already messy enough.If you have knowledge and experience, please help out. If you don't take part you have no justification to complain - you've got to be >>> in it to win it ;-) >> I know we talked about this at the openSUSE conference, and I'm glad that you are starting to kick this off, it's great. >> >> But, what specific machine are you targeting this to run on to start with? We need some kind of specific platform to aim for besides a semi-vague processor level, in order to get a valid kernel and >> tool-chain up and running. The kernel specifically is going to be a bit difficult as each individual platform needs tweaks in order to have it work properly due to the lack of discoverable busses (device-tree work notwithstanding). >> >> In other words, what box do I need to go buy in order to help make this possible? :) > > I think we need more than 1 board to check the port. I think Beagleboard, Beagleboard xM or a Pandaboard could be a nice board to develop openSUSE on ARM (in addition to qemu). > > Firstly, we have to decide what kind of ARM processor we want to support. I think we should target ARMv7 and above Application processor family (Cortex A8, A9 and above) to have enough "power" to run openSUSE. I think we will have poor performances with ARMv5 for openSUSE. > Then, we have to decide which optimization (in GCC) we want to enable. I would say : > - ARM EABI with ARMv7-a instructions > - VFP (vector floating point) > - thumb/thumb2 instructions if possible (some packages do not compile with thumb or thumb2 enabled) > - NEON (not all processor have it, maybe enable it as an option for video libraries for examples to have good performances) I think that if you look at the time that it'll take to have a stable distro, I think it would be best to focus on the Cortex A9 (hardfp etc) with or without NEON. Why start with a distro that is already based on "old" hardware. Nearly all tablets are using a Cortex A9 (mostly in the form of a Tegra 2). That has one small downside. This one doesn't have a NEON FPU at least not one that meets the full specs. What are the plans for a openSuSE ARM distro. Where should it run on? I think as a distro it would be useful to have it running on a tablet like the Asus Transformer and upcoming ARM Cortex A15 servers. > > Interesting pages: > http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores > http://en.wikipedia.org/wiki/ARM_architecture > > I have experiences in embedded Linux and I have a beagleboard xM, so I can help if you want. But I have no experiences in RPM packaging. I would like to take part. I have Pandaboard (OMAP4430) and Toshiba AC100 (Tegra2). > > AFAIK, someone worked on ARM port some time ago in google summer of code. It could be nice to know what have been done. > > Cheers, > > Guillaume Joop. -- 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-arm] Re: Growing some openSUSE ARMs
by Greg KH 22 Sep '11

22 Sep '11

On Thu, Sep 22, 2011 at 05:15:35PM +0200, J.Witvliet(a)mindef.nl wrote: > -----Original Message----- > HP has some small general purpose ARM-boxes. See: > http://h18000.www1.hp.com/products/quickspecs/13500_na/13500_na.HTML > > They are around $100,-- What about something that is actually supported in the community like: http://pandaboard.org/ I think I even might have one of those around here somewhere in my "big pile of hardware"... greg k-h -- 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] Is KDE3 illegal?
by Ilya Chernykh 22 Sep '11

22 Sep '11

I received numerous bugreports regarding KDE3 packages from the legal team. It is very strange given that the packages are essentially the same as were packaged in openSUSE previously. One such bugreport says: https://bugzilla.novell.com/show_bug.cgi?id=719453 === ksim and kgpg contains the GPL-2.0 files listed below. I can't immediately see from the spec file where the source code is compiled into but the spec file should definitely denote the package (or subpackage of applicable) as GPL-2.0. kdeutils-3.5.10/kgpg/conf_encryption.ui.h kdeutils-3.5.10/kgpg/keyexport.ui.h kdeutils-3.5.10/kgpg/kgpgrevokewidget.ui.h kdeutils-3.5.10/kgpg/newkey.ui.h kdeutils-3.5.10/ksim/monitors/lm_sensors/NVCtrl.c kdeutils-3.5.10/ksim/monitors/lm_sensors/NVCtrl.h kdeutils-3.5.10/ksim/monitors/lm_sensors/nv_control.h kdeutils-3.5.10/superkaramba/examples/taskBar/cleanbar/README Also, there are numerous header files in klaptopdaemon licensed under the MPL-1.0 (which is incompatible with the GPL-2.0). Please check if these files are used. If they are, we need to determine how we can resolve the GPL compatibility issue. kdeutils-3.5.10/klaptopdaemon/linux/bulkmem.h kdeutils-3.5.10/klaptopdaemon/linux/ciscode.h kdeutils-3.5.10/klaptopdaemon/linux/cisreg.h kdeutils-3.5.10/klaptopdaemon/linux/cistpl.h kdeutils-3.5.10/klaptopdaemon/linux/cs.h kdeutils-3.5.10/klaptopdaemon/linux/cs_types.h kdeutils-3.5.10/klaptopdaemon/linux/driver_ops.h kdeutils-3.5.10/klaptopdaemon/linux/ds.h kdeutils-3.5.10/klaptopdaemon/linux/ftl.h kdeutils-3.5.10/klaptopdaemon/linux/k_compat.h kdeutils-3.5.10/klaptopdaemon/linux/mem_op.h kdeutils-3.5.10/klaptopdaemon/linux/memory.h kdeutils-3.5.10/klaptopdaemon/linux/ss.h === If the licenses of the components of KDE3 are incompatible with each other how it happened that so many distributions included KDE3? Did all of them break the law? Should we reconsider these legal issues after KDE3 has been already published and included in distributions for years? How can it turn that much-used and beloved software at once becomes "illegal"? -- 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] systemd is being removed from Tumbleweed
by Greg KH 21 Sep '11

21 Sep '11

Due to a number of interdependancies on packages that are not ready for Tumbleweed, and other interactions with the system that are causing problems for some users, I'm going to remove systemd from Tumbleweed today to allow the developers to spend more time on getting it stable for Factory and 12.1 instead of having to chase down problems that are specific to Tumbleweed only. So if you have installed systemd in Tumbleweed, I suggest you now remove it with a simple: zypper rm systemd thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 24

[opensuse-factory] Incorrect changes file
by Ilya Chernykh 21 Sep '11

21 Sep '11

What's wrong with this changes file? https://build.opensuse.org/package/view_file?file=kde3-ktorrent.changes&pac… It does not pass the check. -- 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] Running Qt applications as root bug, not present in XFCE
by Roger Luedecke 21 Sep '11

21 Sep '11

Running Qt applications as root bug, not present in XFCE. It uses the correct widget set and colors. Looks to me like we can fix the bug by seeing how YaST gets its setting info from XFCE and comparing what is different between it and KDE. -- 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] Factory Xorg packages
by Michael Powell 21 Sep '11

21 Sep '11

After this mornings updates which include some new various Xorg packages: >From /var/log/messages: Sep 15 06:16:04 workstation kdm[1112]: X server died during startup Sep 15 06:16:04 workstation kdm[1112]: X server for display :0 cannot be started, session disabled >From /var/log/Xorg.0.log: [ 11.167] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 11.167] (II) Module nvidia: vendor="NVIDIA Corporation" [ 11.167] compiled for 4.0.2, module version = 1.0.0 [ 11.167] Module class: X.Org Video Driver [ 11.167] ================ WARNING WARNING WARNING WARNING [ 11.167] This server has a video driver ABI version of 10.0 that is not supported by this NVIDIA driver. Please check http://www.nvidia.com/ for driver updates or downgrade to an X server with a supported driver ABI. [ 11.167] ================================================================= [ 11.167] (EE) NVIDIA: Use the -ignoreABI option to override this check. [ 11.167] (II) UnloadModule: "nvidia" [ 11.167] (II) Unloading nvidia [ 11.167] (EE) Failed to load module "nvidia" (module requirement mismatch, 0) [ 11.167] (EE) No drivers available. [ 11.167] Fatal server error: [ 11.167] no screens found In xorg.conf adding this: Section "ServerFlags" Option "IgnoreABI" "true" EndSection Produces this: [ 11.124] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 11.125] (II) Module nvidia: vendor="NVIDIA Corporation" [ 11.125] compiled for 4.0.2, module version = 1.0.0 [ 11.125] Module class: X.Org Video Driver [ 11.125] ================ WARNING WARNING WARNING WARNING [ 11.125] This server has a video driver ABI version of 10.0 that is not supported by this NVIDIA driver. Please check http://www.nvidia.com/ for driver updates or downgrade to an X server with a supported driver ABI. [ 11.125] ================================================================= [ 11.125] (WW) NVIDIA: The driver will continue to load, but may behave strangely. [ 11.125] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 12.2, need < 12.0). The driver will continue to load, but may behave strangely. [ 11.125] (II) NVIDIA dlloader X Driver 260.19.44 Sun Feb 27 22:42:21 PST 2011 [ 11.125] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 11.125] (++) using VT number 7 [ 11.240] (II) Loading sub module "fb" [ 11.240] (II) LoadModule: "fb" [ 11.241] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 11.241] (II) Module fb: vendor="X.Org Foundation" [ 11.241] compiled for 1.10.4, module version = 1.0.0 [ 11.241] ABI class: X.Org ANSI C Emulation, version 0.4 [ 11.241] (II) Loading sub module "wfb" [ 11.241] (II) LoadModule: "wfb" [ 11.241] (II) Loading /usr/lib64/xorg/modules/libwfb.so [ 11.241] (II) Module wfb: vendor="X.Org Foundation" [ 11.241] compiled for 1.10.4, module version = 1.0.0 [ 11.241] ABI class: X.Org ANSI C Emulation, version 0.4 [ 11.241] (II) Loading sub module "ramdac" [ 11.241] (II) LoadModule: "ramdac" [ 11.241] (II) Module "ramdac" already built-in [ 11.241] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 11.241] (II) Loading /usr/lib64/xorg/modules/libwfb.so [ 11.241] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 11.241] Backtrace: [ 11.241] 0: /usr/bin/Xorg (xorg_backtrace+0x26) [0x462286] [ 11.241] 1: /usr/bin/Xorg (0x400000+0x66819) [0x466819] [ 11.241] 2: /lib64/libpthread.so.0 (0x7f72b3e34000+0xfce0) [0x7f72b3e43ce0] [ 11.241] 3: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f72b0e30000+0xae000) [0x7f72b0ede000] [ 11.241] 4: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f72b0e30000+0x3b63ea) [0x7f72b11e63ea] [ 11.241] 5: /usr/bin/Xorg (xf86DeleteScreen+0x7c) [0x470d8c] [ 11.241] 6: /usr/bin/Xorg (InitOutput+0xbd2) [0x4761f2] [ 11.241] 7: /usr/bin/Xorg (0x400000+0x270c3) [0x4270c3] [ 11.241] 8: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f72b2dac21d] [ 11.241] 9: /usr/bin/Xorg (0x400000+0x2756d) [0x42756d] [ 11.241] Segmentation fault at address 0x18 [ 11.241] Fatal server error: [ 11.241] Caught signal 11 (Segmentation fault). Server aborting [ 11.241] [ 11.241] This backtrace in particular is from Nvidia driver version 260.19.44. The overall Xorg server failing to start was observed in 260.19.44, 280.13, and the 285.03 Beta. Apparently there is ABI breakage between the new Xorg packages and Nvidia proprietary "blah.run" drivers from the Nvidia web site. -Mike -- 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] monodevelop
by Nelson Marques 21 Sep '11

21 Sep '11

Hi all, I've noticed that monodevelop 2.4 is broken on openSUSE Factory. When I try to launch it I get the following error: "System.NullReferenceException: Object reference not set to an instance of an object at GLib.Object.NotifyCallback (IntPtr handle, IntPtr pspec, IntPtr gch) [0x00000] in <filename unknown>:0 " There is also a new release available, 2.6.0.1 (http://monodevelop.com/Download). Anyway we can have this updated ? NM -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 3

[opensuse-factory] install_info_prereq macro
by Ruediger Meier 21 Sep '11

21 Sep '11

Hi, I see a lot (if not all) SUSE packages with info docs inside are using PreReq: %install_info_prereq But this is a SUSE only macro making spec files non portable and actually it just expands to "info". Is there any good reason why we should still use the macro rather than simply "info"? cu, Rudi -- 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] drivers:webcam
by Duncan Mac-Vicar P. 21 Sep '11

21 Sep '11

Drivers like gspcav1 do not build on 11.x and rpm -ql kernel-desktop | grep gspca Tells me they seem to be now included in the kernel. Same with sn9c20c and uvcvideo r5u870, spca5xx-kmp and others do not build for newer distros, but they don't seem to be included in the kernel anyway. Anyone against on disabling gspcav1, sn9c20c and uvcvideo where they don't build? -- Duncan Mac-Vicar P. - http://www.suse.com/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- 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] Internal compiler error at 64-bit
by Ilya Chernykh 20 Sep '11

20 Sep '11

Hi! I receive permanent internal compiler error when building for 64-bit in this package: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=kde3-… The error message: ./maindlg.ui.h: In member function 'virtual void maindlg::btnLoad_clicked()': ./maindlg.ui.h:387:68: warning: ignoring return value of 'int fscanf(FILE*, const char*, ...)', declared with attribute warn_unused_result ./maindlg.ui.h:389:96: warning: ignoring return value of 'int fscanf(FILE*, const char*, ...)', declared with attribute warn_unused_result ./maindlg.ui.h:397:61: warning: ignoring return value of 'int fscanf(FILE*, const char*, ...)', declared with attribute warn_unused_result curvedlg.moc: In constructor 'matdata::matdata()': curvedlg.moc:155:86: internal compiler error: Aborted For 32-bit it builds well. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 9

[opensuse-factory] KDE-Telepathy
by jdd 20 Sep '11

20 Sep '11

Hello :-) wil KDE-Telepathy be made available in final 12.1 (I'm writing the release notes) thanks jdd -- http://www.dodin.net http://www.youtube.com/user/jdddodinorg http://jdd.blip.tv/ -- 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] AppArmor 2.7 in factory - please test!
by Christian Boltz 20 Sep '11

20 Sep '11

Hello, AppArmor 2.7 (beta1) is in Factory since some hours. Short version: please test it and report any problems you notice. Long version: I'm quite new in maintaining the AppArmor package (I became maintainer last saturday ;-) Additionally, I dropped a 380k patch that changed the whole upstream buildsystem to use automake [1]. In other words: the whole build process of the AppArmor package is totally new, and it might be that this introduced some regression I didn't notice yet. A known "regression" is that the tomcat_apparmor package is no longer built - it is unmaintained upstream since quite some time and failed to build. If anyone needs this, please step up and help maintaining it ;-) Please test if the AppArmor 2.7 beta1 package works as expected on your system - if not, please reply to this mail or open a bugreport. (Success reports are also welcome, of course.) If you don't have a Factory installation available, you can also download packages for 11.3 and 11.4 from security:apparmor:factory. In theory, they should work on those systems without changing the kernel side, but I can't promise that ;-) (they seem to work on my 11.4 system) Finally: thanks to everybody who helped me to get the AppArmor package updated by personal support on the conference and online support on IRC. Regards, Christian Boltz [1] I don't really know automake and upstream isn't too interested in this patch[2], therefore I decided to drop it. (The patch is still included in the sources in OBS, but disabled - just in case someone wants to update it and push it upstream.) [2] it only applies to 2.6.1, not to 2.7 - and it looks like nobody wants to update such a big patch, so it's understandable -- ``Hello, my userid is root and if you feed me caffeine, nobody gets hurt.'' -- AdB -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 13