April 2011 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] No debuginfo packages in Tumbleweed:KDE
by richard -rw- weinberger 29 Apr '11

29 Apr '11

Hi, Is it intended that Tumbleweed:KDE does not contain debuginfo packages? As some KDE apps keep crashing and crashing these packages are very useful to file sane bug reports... -- Thanks, //richard -- 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] openSUSE Tumbleweed status for the week of April 9, 2011
by Greg KH 29 Apr '11

29 Apr '11

Here's a short note as to the status of some recent activity in the openSUSE:Tumbleweed repo: - the kernel is at the 2.6.38 release level - a number of multimedia packages and libraries were updated to their Factory level - Banshee 2 is now in the repository - LibreOffice 3.3.2 is in the repository. - I'm considering adding GNOME:3.0 to openSUSE:Tumbleweed when the openSUSE GNOME developers release it. It's building in a test repository right now pretty successfully, but it might be a few more weeks until it seems "ready" enough. Note, it seems that when _any_ package is added or updated in the openSUSE:Tumbleweed repository, LibreOffice rebuilds itself. This can be annoying for those on bandwidth-challenged network connections, and seems to be due to the dependency chain that the LibreOffice developers have defined in their .spec files. Hopefully this will be resolved for the next major release, but in the meantime, I'll try to limit library updates in openSUSE:Tumbleweed to once a week at the most unless security issues require it. 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

13 37

[opensuse-factory] PySide for openSUSE
by Mariusz Fik 29 Apr '11

29 Apr '11

Hello, since PySide[1] is ready for production use[2] with release >= 1.0 it would be good to have it in the next openSUSE release. So far we have the latest PySide packages (and tools used for building) in cgoncalves' home project [3]. PySide provides LGPL-licensed Python bindings for the Qt. What do You thing about pushing PySide to Factory? Is it worth? If yes, what devel project should we use for PySide packges, devel:languages:python? Or make a request for a new sub-project? [1]:http://www.pyside.org/ [2]:http://developer.qt.nokia.com/wiki/PySide_FAQ#fb64e4e3a92dd7b4d3629e5bd6… [3]:https://build.opensuse.org/project/show?project=home%3Acgoncalves%3Apysi… -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member

3 2

[opensuse-factory] new osc release 0.131
by Adrian Schröter 27 Apr '11

27 Apr '11

A new osc release is out. Beside the usual stack of bugfixes, this version comes with a larger number of functionality for our upcomming OBS 2.3 release. The request and especially the review handling of requests has been improved, what should help esp. people who work on openSUSE:Factory packages. Also a number of new commands for our upcomming maintenance features have been added. These will get explained in more details in our OBS book. This release is only available via openSUSE:Tools project for now, we will roll out an official update for all distributions during OBS 2.3 beta phase. http://download.opensuse.org/repositories/openSUSE:/Tools/ Detailed Release Notes: ======================= - new command 'develproject' to print the devel project from the package meta. - add blt and rblt commands, aka "buildlogtail" and "remotebuildlogtail" to show just the end of a build log (for getting the fail reason faster). CHANGE: the --start parameter is now called --offset - add "createrequest -a add_group" option to create a group request - add "createrequest -a add_me" shortcut - add "less" command, doing the same as "osc cat" but with pager - fallback to unexpanded diff mode on "osc diff" on merge error. - support viewing the commit history of deleted packages - show review states on "review list" - new source service commands "localrun" and "disabledrun" to generate files without _service: prefix - add "request supersede" and "review supersede" to supersede with existing request - make it possible to run single source services, even when not specified in _service file. (For example for doing a version update without creating a _service file: osc service lr update_source) - protect rebuild and abortbuild commands with required "--all" option to mass failures by accident (similar to wipebinaries) - "review accept/decline" is trying to change all reviews of a requests, if a specific one is not specified by user # # Features which requires OBS 2.3 # - "my requests" is doing faster and complete server side lookup now if available - "review" command has been extended to handle reviews by project or by package maintainers - support for new source service modes: disabled, trylocal and localonly - support project wide source services - support for armv7hl architecuture. used to denote armv7 + hardfloat binaries - add force option to accept requests in review state. - add "maintenancerequest" command to request a maintenance incident from maintenance team - add "releaserequest" command run a maintenance update release process (for maintenance team only) - allow to force the storage of project meta data (to ignore depending repositories for example) - "my requests" is showing requests with open reviews also now -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] netdiscover
by jdd 27 Apr '11

27 Apr '11

Hello, I sometime have to scan my network to know what is the IP of some active box like a smc router. smc gives only a windows utility. It's probably pretty easy to do by hand with arp utilities, but I'm not skilled enough to this an Ubuntu fellow uses "netdiscover" (http://sourceforge.net/projects/netdiscover/) I could easily compile it (it needs libpcap-devel and libnet-devel available from YaST) is there a reason not to have it in openSUSE (other than "nobody cared to package it - what I will understand)? if not, where can I best ask for having it included? Bugzilla? Fate? 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 5

[opensuse-factory] gcc error
by Donn Washburn 27 Apr '11

27 Apr '11

How come I see this error all the time and some else ofn this list doesn't. Both of us have x86-64 openSuSE Factory systems. -- 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

3 2

[opensuse-factory] RPM 4.9.0 and needed changes in spec files
by Cristian Morales Vega 27 Apr '11

27 Apr '11

Since I got no answer in -packaging (http://lists.opensuse.org/opensuse-packaging/2011-03/msg00050.html) trying here. What's the plan for RPM in openSUSE 12.1? RPM 4.9.0 was released nearly two month ago and Factory still uses 4.8, I would rather prefer to start adapting the spec files now than later. I suppose Vincent continues modifying spec files with his new macros, it would be ugly to say him all the work needs to be undone at the last moment. The first step would be informing packagers of any new rules. Looking at the release notes I see two important points: * "Dependency generators are now pluggable. Arbitrary number of dependency types is supported, new types can be added through a drop-in directory and file classification is now done with a combination of path and libmagic-type include/exclude regular expressions (XXX add link to documentation once it exists)" How they exactly work? Something should be changed about %wx_requires? * "EXPERIMENTAL support for package "collections" which are sort of like named triggers that only run once within a transaction. This can be used for example to avoid redundant calls for cache updates etc. (XXX add link to documentation once it exists)" Experimental? Should we use this instead of multiple calls to gtk-update-icon-cache? It's expected that openSUSE 12.1 will use a newer RPM where collections are no longer experimental? And this would be nice: * "Short-circuiting binary builds is now allowed by rpmbuild for developer convenience while testing. Short-circuited packages are tainted with an unsatisfiable dependency to limit their use for the intended testing-only purpose." How? Is this possible through "osc build"? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 11

[opensuse-factory] openSUSE Tumbleweed status for the week of April 22, 2011
by Greg KH 27 Apr '11

27 Apr '11

Here's a short note as to the status of some recent activity in the openSUSE:Tumbleweed repo: - new kernel updates tracking the upstream stable 2.6.38 releases. - lxde (and its sub-packages) was added - calibre was added - other smaller packages were added - KDE update seems stable and working. It's in the openSUSE:Tumbleweed:KDE repo if anyone wants to test it out now. I'll be working next few weeks to merge this into the main openSUSE:Tumbleweed repo as my bandwidth allows. - There is a GNOME 3.0 Tumbleweed repo at openSUSE:Tumbleweed:GNOME. It's properly building right now, but the same caveats remain for the main GNOME 3.0 repo (i.e. network manager issues with KDE, and other minor stuff), so I can't merge it to the main openSUSE:Tumbleweed repo just yet. I'll wait for these changes to settle down, but if you want, feel free to try out the repo for your GNOME 3.0 systems running Tumbleweed. I'll keep it up to date as the changes merge into the main GNOME 3.0 repo. - artwork questions were raised with one proposed logo already sent in. More to come in this area hopefully soon. - There were a few "version downgrades" that happened as the upstream project release number was changed to reflect the basesystem release number correctly. This will probably continue to happen as this change is propagated throughout the openSUSE build system to fix up these errors by the various developers. You can safely ignore them when they happen. As always, if anyone knows of any packages they wish to see added to Tumbleweed, please let me know. 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

3 5

[opensuse-factory] gcc 4.6.0 in Tumbleweed
by Marco Poletti 27 Apr '11

27 Apr '11

Are there any plans to push gcc 4.6.0 in Tumbleweed (now or later)? I haven't tried it yet, so I can't guarantee it is stable enough. Thanks, Marco Poletti -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

6 8

[opensuse-factory] Radeon Gallium Driver ?
by Vincent Lejeune 26 Apr '11

26 Apr '11

Hi, Opensuse still use classic Mesa driver for hardware acceleration on radeon driver ; there are actually 2 mesa drivers for radeon, r300 and r600, and both come with 2 version : classic Mesa (r300c and r600c) and Gallium3d Mesa (r300g and r600g). Radeon developpement have switched to the gallium3d drivers in Mesa. r300g is considered as stable, r600g is still considered as "experimental", however my own tests show that it is more stable than r600c (less rendering error in gnome 3/kwin compositor). Besides, both drivers show a +20% performance increase over their classic Mesa counterpart. I tested it on a Zacate APU, it ships with a radeon 6350 gpu ; thus I think that support is ok even for newly released hardware part. Some distributions (like ubuntu) have already switched to r300g, and I think that others might switch soon to r600g. Maybe it would be wise to consider a switch to gallium version of both drivers for next opensuse version too ? Regards, Vincent -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 6