openSUSE Factory January 2012

factory@lists.opensuse.org

88 participants
63 discussions

[opensuse-factory] Export broken for KinfoCenter
by Roger Luedecke 30 Jan '15

30 Jan '15

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

2 1

Re: [opensuse-factory] Nothing provides /usr/bin/php5
by Sascha Peilicke 11 Jan '14

11 Jan '14

On 12/01/2011 11:44 AM, Kyrill Detinov wrote: > > Hello. > > We have one package affected in standard repo: leechcraft-eiskaltdcpp. > The program itself doesn't require php5. But the package includes > example scripts with shebang '!/usr/bin/php5'. So the package isn't > installable. > > Also I see the same problem with pgfouine from Contrib (written in > PHP) and eiskaltdcpp from filesharing repo. Maybe more in third-party > repositories. > > Can we have symlink /usr/bin/php -> php5 in php5 package? Or affected > packages should be fixed? > Please file a bug against php5 and assign to Cristian Rodríguez. -- Viele Grüße, Sascha -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

[opensuse-factory] KDE menus and gitorious
by Cristian Morales Vega 06 Nov '12

06 Nov '12

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

4 6

[opensuse-factory] please fix non PIE setuid binaries
by Ludwig Nussel 24 Feb '12

24 Feb '12

Hi, The following packages in Factory have setuid binaries that are not compiled with position independent code according to rpmlint. I'd like to make the check (non-position-independent-executable ) fatal on March 1st. I'll also file bugs for the individual packages. chromium cifs-utils dbus-1 eject fuse gnokii i4l-base jfbterm kdebase3 libgnomesu majordomo mc mgetty mtr open-vm-tools opie pcmciautils pdns polkit rp-pppoe scotty sudo su-wrapper thttpd uucp virtualbox vte zypper cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

16 50

[opensuse-factory] [RFC DRAFT] Phasing out sysvinit
by Cristian Rodríguez 08 Feb '12

08 Feb '12

Hi: Supporting 2 different init systems comes with a large increase of possible usecases and scenarios that are very difficult to support correctly, specially in the long term. This RFC proposes steps to permanently phase out sysvinit from future openSUSE releases. Phase 0 - Fix all *currently* outstanding bugs of systemd if any, note that this step only deals with problems in systemd itself, not in service files installed by other packages, udev, kernel, networkmanager or whatever other thing. - Determine which services currently lack of native systemd units. - Add an rpmlint error with moderate badness for the start,complaining about the lack of unit files. Phase 1: - Delete sysvinit scripts that deal purely with hardware things,like only loading kernel modules, making udev to handle them or simple dropping a foobar.conf with the needed modules in /usr/lib/modules-load.d/ whichever is more adequate or doable. - Add missing systemd units for the packages where rpmlint warns. - Add rpmlint with badness complaining about logrotate, or other shell scripts calling files in /etc/init.d ... Phase 3: - Turn rpmlint warnings about the lack of systemd units on packages including traditional sysvinit scripts a fatal error. - fix logrotate or shell scripts that are calling sysvint scripts and make the rpmlint warning a fatal error. - tell RPM to %exclude files in /etc/init.d from packages, do not forc packagers to exclude these files themselves. - make all macros relevant to traditional init scripts a no-op, do not force packagers to remove those lines or add extra hacks to the already horrendous hackery in spec files. - test, test, test. - remove sysvinit and all the relevant bootloader options and from the documentation. -- ????? -- Profit. :-) This is just a quick brain dump, I am certainly missing something else. Have fun. Cristian. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

53 224

[opensuse-factory] moving everyting to /usr
by Greg KH 02 Feb '12

02 Feb '12

Here's a good document describing the why behind this type of change: http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge It's something that I think we should push for 12.2 if at all possible. 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

13 19

[opensuse-factory] KDE4.8/QT bug is still there
by C 02 Feb '12

02 Feb '12

This bug seems to be getting worse with each release of KDE4 :-( Reported here: https://bugs.kde.org/show_bug.cgi?id=275469 and here: https://bugs.kde.org/show_bug.cgi?id=292057 Basic symptoms: - open an application, and it may or may not actually show up in the Task Manager/Panel - close an application and it may or may not be removed from the Task Manager/Panel It essentially makes the Task Manager unreliable and unusable. The KDE guys say it's a bug in QT and there's nothing they can do about it beyond referring it upstream to QT. There appears to be some patches in the works - is there anything we can do from our side to speed this up.. or include the patches (backporting?) to make KDE4 more usable. I've got one more to add to the list - run a full screen application (game) and when you return to the desktop, the panel and the entire desktop will not respond to click for up to 30 seconds although the mouse is working fine, and if I Alt+Tab I can open/use apps that were minimized. At some point, 30 to 45 seconds after exiting the full screen app (game), the desktop is repainted and becomes responsive again. All clicks you made during that period appear to be queued up and a whole lot of things happen at once as things catch up. I haven't yet found a bug report at KDE for this one... not sure on the right keywords for searching. Will keep trying :-P C. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] Tumbleweed open for suggestions
by Greg KH 01 Feb '12

01 Feb '12

As some of you might have noticed, openSUSE:Tumbleweed has woken up from its holiday break, and is starting to update. But, right now the list of packages are pretty small, basically stuff I use and rely on (kernel, vim, mutt, etc.) I need suggestions of packages to add. Of course, the usual rule of "the package must already be in openSUSE:Factory" still applies. Suggestions? 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

12 35

[opensuse-factory] The 4.8 login manager does not satisfy the quality look that openSUSE is known for
by Roman Bysh 31 Jan '12

31 Jan '12

Hello Mates, Does anyone think the login manager provided with 4.8 is as good as openSUSE's manager in 4.7? Not as slick. What can be done to improve the look? Cheers! Roman ------------------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux ------------------------------------------------- http://counter.li.org #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 11

[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 31 Jan '12

31 Jan '12

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

5 5

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory January 2012