openSUSE Factory November 2011

factory@lists.opensuse.org

151 participants
202 discussions

[opensuse-factory] Export broken for KinfoCenter

by Roger Luedecke

Export button is greyed out no matter what. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 years, 7 months

[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

8 years, 10 months

[opensuse-factory] Lilypond won't work with guile 2.0, What can I do to prevent it being dropped? Do we really want guile 2.0 yet?

by Dave Plater

OpenSUSE has jumped way ahead of all the other major distributions by pushing guile-2.0 to factory, this may cause problems for packages such as gnucash if it uses guile to the extent that lilypond does. Lilypond uses guile extensively and are working on porting lily to guile 2.0 but this is their timeline quoted from one of my emails from Graham Percival to the devel list please note that lilypond 2.16.0 may not be released before openSUSE 12.1 and I'm working on 2.14.2 atm the current release : There is absolutely zero chance of lilypond 2.16 using guile 2.0. There is maybe a 10% chance that any version of lilypond will support guile 2.0 in 2011. Total guesswork for future predictions: 50% chance of supporting guile 2.0 before July 2012, 80% chance of support guile 2.0 before the end of 2012. What that means for opensuse is up to you. If you particularly want guile 2.0, then by all means jump in; the more people working on it, the higher the chances are that it'll get done sooner. But based on the amount of work that currently goes into guile 2.0, those are my estimates. Cheers, - Graham and I think this is also relevant, another lily developers reply from the same message: Given that the upcoming ubuntu oneiric apparently does not include guile 2.0, I also don't see a switch to guile 2.0 in the near future. I suppose that we should ask the ubuntu people when they'll finally package guile 2.0. Cheers, Reinhold I've looked at parallel installation of guile 1.8.8 (we jumped from 1.8.7 to 2.0.1) and it doesn't look easy otherwise I would have submitted guile1 but I'm still working on it although I'm not that familiar with the autoconf/automake build system at this level. What this means for openSUSE, lilypond is a very popular musical notation type setting program, the developers pride themselves in the accuracy of the notation positions, it is also used, for musical notation by rosegarden, a popular music and midi composition program. Both of these applications have no substitutes in the open source world and only have costly equivalents in the ms windows world, neither being available for ms windows although there are requests to port for both this won't happen in the immediate future. Rosegarden can work without lilypond as it is only bound to lilyponds notation fonts but the sheet music it exports will be useless so it will lose major functionality. Lilypond won't even be able to be installed via tarball on openSUSE 12.1 without the user removing guile 2.0 completely and installing guile 1.8 via tarball, as a result these users of lilypond and rosegarden will drop openSUSE. I started as a community maintainer by saving both lilypond and rosegarden from being dropped, I'm now very active in maintaining multimedia apps and libs and losing these programs will mean losing a large section of professionals in music related professions that have migrated from the windows world including the people that I've converted from ms windows just by showing them rosegarden although ms's change from xp to vista also helped. For the other packages that directly depend on guile : guile aisleriot gnucash autogen and slib, the change back to guile-1.8.8 won't AFAICS have any negative effects, all of these packages simply have patches for guile 2.0 and after looking at the patches, will most probably build with the patches still in place. I don't know what the situation is with guile users but it is an app for use by apps and not a direct users app. Guile-1.8.7 builds for factory, guile-1.8.7 doesn't build for 11.4. What are we going to do? Drop lilypond, I will keep it alive in home:plater:lilypond with guile-1.8.8 to replace guile-2.0.2 or revert to guile-1.8.8 in line with the other linux distributions? Thanks Dave Plater -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

9 years, 7 months

[opensuse-factory] proper way to link packages in openSUSE:Tumbleweed

by Greg KH

Hi Adrian, We talked at brainshare about the "correct" way to link packages in Tumbleweed, and unfortunatly, I forgot one of the steps as I can't get it to work now. Here's what I remember: - look up the xsrcmd5 from the "root" package. For example, in the X11:xfce midori package I would do something like: osc api /source/X11:xfce/midori | grep linkinfo | pick out xsrcmd5 (where 'pick out' is a regex) - then run 'osc setlinkrev' with that md5 in the Tumbleweed repo. It's that last step that I can't seem to get correct, what is the exact command for it? I tried something like: $ osc setlinkrev -r bc383278250a5673d3799c2b31c9e6ef openSUSE:Tumbleweed filesystem setting revision to bc383278250a5673d3799c2b31c9e6ef for package filesystem Server returned an error: HTTP Error 400: Base System/filesystem/bc383278250a5673d3799c2b31c9e6ef not in repository. Either not existing or misconfigured server setting for '$nosharedtrees' setting in BSConfig.pm Base:System/filesystem/bc383278250a5673d3799c2b31c9e6ef: not in repository. Either not existing or misconfigured server setting for '$nosharedtrees' setting in BSConfig.pm Any hints would be appreciated. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 8 months

[opensuse-factory] [12.1] massive data loss in /var/tmp/

by Melchior FRANZ

Apparently, 12.1 has added /var/tmp/ to TMP_DIRS_TO_CLEAR in /etc/sysconfig/cron. I was quite surprised when I found out today that I've lost a few GB of data, which used to be safe there. Needless to say that I'm not pleased. No backups, because it wasn't *that* important, but I find such changes without warning suboptimal, to put it politely. m. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 8 months

[opensuse-factory] Planned submission of glib 2.31 and resulting package failures

by Dimstar / Dominique Leuenberger

Hello everybody! This is as a heads up for all of you having packages depending (directly or indirectly) on glib. We're like to start pushing parts of GNOME 3.3.2 to Factory in the not too distant future. A 'critical' part will be glib, which gets updated to version 2.31, and, in turn, get's very strict on its header inclusion. With the exception of very few headers (see end), only glib.h can be #include'd now; all the others trigger an error: error: "Only <glib.h> can be included directly." Generally, the code needs fixing and changing the includes to only contain #include <glib.h> Most of the other glib headers are indirectly implicit included. So far I know of those that still need to be manually included: glib/gstdio.h glib/gi18n.h glib/i18n-lib.h I'll be trying to setup a repo like coolo does for the various fallouts he produces (libtool/automake) and try to get a bunch of packages fixed beforehand (I fixed most of GNOME:Factory/GNOME:Apps by now), but of course I'll gladly accept any help of other volunteers checking their packages. Best regards, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 8 months

[opensuse-factory] Proposal for 12.2, move all binaries under /usr

by Greg KH

Hi all, As a proposal for 12.2, I would like to implement the move of all binaries to /usr/ like is being done at the moment in Fedora. Here's the details as to why this is a good thing to do, and what is involved in it: https://fedoraproject.org/wiki/Features/UsrMove The first packages implementing this have already started to land in Fedora's version of Factory. Before you get worried, there will be symlinks back to /bin and /sbin for those scripts expecting things to be in those locations. We can use the Fedora patches for almost all of this, they are all published at: http://harald.fedorapeople.org/downloads/usrmove/ and a number of upstream projects are already moving their releases over to this as well, which will make things easier. If there are no major objections, I'll start working on Base:system in December. thanks, greg k-h p.s. Please, before you respond, read the link above and all of the discussion about it and don't repeat the same questions that the link already answers. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 8 months

[opensuse-factory] Still openSUSE 12.1 - NetworkManager does it worst....

by Kim D. Leyendecker

Howdy all, *Before* reading my mail, please note: openSUSE 11.4 ran perfect on my machine, after the upgrade to 12.1, networkmanager doesn't run at all.I can't connect to my router anymore (which worked yesterday, even with 12.1). The result is a completely angry user, who just wants his sane and working 11.4-like system back. Please excuse my offending mail, but I'm boiling totally. My problem: After the upgrade, NetworkManager doesn't ran anymore. I did some searching and fixed the problem. Now, today, I started my machine but NM can't connect anymore. It just says something like: Wait for authorization On 11.4 it used to be KWallet which asked my a password for NM. With 12.1 it's a KDE-su like one. Does anyone else has the problem? I'm writing from my notebook because my workstation isn't connected anymore. Please, can you help me? thanks, --kdl -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 9 months

[opensuse-factory] Pull down menu platform in bugzilla is missing openSUSE 12.1 and openSUSE 12.2

by Freek de Kruijf

The pull down menu in a bugzilla bug report page for the platform does not have an entry for openSUSE 12.1 and with factory around also not for openSUSE 12.2 or if you prefer openSUSE Factory. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 9 months

[opensuse-factory] libgadu and kdenetwork

by todd rme

I have been trying to get kdenetwork to detect libgadu for gadu protocol support without success. libgadu is available, and it is in the buildrequires. Here is the cmake message: -- checking for module 'libgadu' -- found libgadu, version 1.11.0 -- Found LIBGADU: /usr/lib64/libgadu.so grep: /usr/local/include/libgadu.h: No such file or directory -- libgadu must be compiled with pthreads support Note that libgadu IS being built with pthreads support enabled. Also note that cmake appears to be searching /usr/local/include/. Include files are not installed there, they are installed in /usr/include/, and kdenetwork is told to search in /usr/include, it searches in /usr/include for every other package it needs, and libgadu.pc says to look in /usr/include. I looked at the cmakelists.txt files and couldn't find anything obviously wrong. Does anyone have any ideas what might be going on here? -Todd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 9 months

Jump to page:

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory November 2011