openSUSE Factory August 2011

factory@lists.opensuse.org

130 participants
135 discussions

[opensuse-factory] KDE menus and gitorious

by Cristian Morales Vega

I created a merge request for desktop-data three weeks ago. It's just a minor patch that doesn't really fix anything but a warning from kbuildsycoca4. I'm not sure about how Gitorious works, maintainers are supposed to notice the "1" in the merge requests section or they receive an email notifying it? And since I'm on it. Since I updated my 11.3 system to KDE to 4.5 the "inline" part of the menu is not honored... Expected behavior? Known problem? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

9 years, 6 months

[opensuse-factory] consolidating the list of mysql flavors in Factory

by Dirk Müller

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

10 years, 8 months

[opensuse-factory] Kernel for 11.4?

by Jeff Mahoney

-----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

10 years, 8 months

[opensuse-factory] IPV6 privacy in openSUSE

by Andreas Jaeger

I wonder whether our IPv6 settings are the right ones after reading the following article (sorry, German only): http://www.heise.de/newsticker/meldung/IPv6-Smartphones-gefaehrden-Privatsp… which references: http://www.heise.de/netze/hotline/IPv6-anonym-1100727.html We set use_tempaddr to 0 by default (disabling privacy extensions) and set it to 1 if enabled. The article advises to use 2. Background: By default (value 0) my IPv6 address will be derived from my hardware (macaddr) and therefore be the same independend how I connect to the internet. So, it's easy to track my computer... So, my proposal is to do the following two changes: * Use 2 instead of 1 in /etc/rc.d/boot.ipconfig for enabling the privacy extensions * Set IPV6_PRIVACY=yes in /etc/sysconfig/sysctl Any concerns with this change? Btw. here's an Ubuntu bugreport: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/176125 and Windows (since XP) is doing it the same way on desktops. Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 8 months

[opensuse-factory] X11-Xorg for factory is still at 1.9.3

by Vincent Lejeune

Hi, xorg-x11-server in Factory is still at 1.9.3 release ; however latest stable release is in 1.10.x branch.... As feature freeze is 2 weeks away, and as an xorg update is not trivial, does that mean that openSUSE 12.1 will keep a 11 months old xorg server in november ? I'm encountering issue with obsolete GL_PROTO extension when trying to compile Mesa from master because of that. Regards, Vincent -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 8 months

[opensuse-factory] Some php5-* packages needed in Factory - please help ;-)

by Christian Boltz

Hello, I plan to submit PostfixAdmin to Factory. One of its dependencies is the Zend Framework, which requires some more packages. I'd like to ask the maintainers of these packages to submit them to Factory ;-) The dependency tree looks like this: php5-ZendFramework php5-APC php5-pear-phpunit php5-pear-channel-phpunit php5-pear-phpunit-DbUnit php5-pear-phpunit-File_Iterator php5-pear-phpunit-Object_Freezer php5-pecl-memcache @maintainers of these packages: can you please submit them from server:php:extensions and :applications to Factory? (If everything else fails, I can try to maintain them in Factory, however my knownledge of these packages isn't as good as it should be.) Notes: - php5-pear-phpunit requires several php5-pear-* packages, which means the SR will have to wait until those were accepted - php5-ZendFramework submission needs to wait until everything else was accepted Thanks in advance for your help! BTW: My temporary project home:cboltz:zend-framework (with a QA package that BuildRequires all the above packages to check if they are installable) might be interesting (it shows that the above list is complete). home:cboltz:prepare-factory can serve as a status monitor to show which packages are still missing in factory. Regards, Christian Boltz -- Weil ich einen Airbag im Auto habe fahre ich ja auch nicht dauernd mit Vollgas gegen einen Baum nur um zu wissen das der Airbag funktioniert. [Uwe Drießen in postfixbuch-users] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 8 months

[opensuse-factory] Status: Milestone5

by Stephan Kulow

Hi, The show stoppers we had this morning are all fixed, so in good hope that the current checkin round will magically make everything perfect, I raised the version to M5, so we can publish it tomorrow. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 8 months

[opensuse-factory] RFC: Replacing default gzip and bzip2 command line tools

by Cristian Rodríguez

Hi: I would like to propose replacing (not removing) the default command line tools for compression, specifically "gzip" for "pigz" and "bzip2" for pbzip2. These tools are backward compatible and have dramatically better performance because they do compression in parallel utilizing current multiple CPU machines. Possible paths to do this a) Simple adding "update-alternatives" support to all the mentioned tools and let the user to decide, however we install pigz and pbzip2 by default. I do not endorse this way. b) Building pigz with executable name "gzip" and rename gzip to gnu-gzip, and bzip2 to bzip2.old or something similar. This is the way endorse c) As these tools are more frecuently used with "tar", make it to prefer the parralel versions, current gnu-tar already tries different implementations when the default ones are not present, would be a matter of altering the order if needed. I take no stance on this way. comments appreciated. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 8 months

[opensuse-factory] Is there a good tool to search patches in SVN?

by Ilya Chernykh

Say browsing by date, search by word etc? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 8 months

[opensuse-factory] Please revert --no-copy-dt-needed-default

by Marcus Meissner

Hi, Please revert --no-copy-dt-needed-default, the fallout is too large. failed/head-ppc$ grep -l "is defined in DSO" *|wc -l 77 Not even cairo or openssh builds. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

10 years, 8 months

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory August 2011