openSUSE Factory March 2013

factory@lists.opensuse.org

119 participants
106 discussions

Re: [opensuse-factory] repository priorities with Tumbleweed

by Thomas Langkamp

> No, please don't confuse people, if you add more repos than just > Tumbleweed you really had better know what you are doing or bad things > can, and will, happen :) I understand. I just would like to add the following to http://en.opensuse.org/Portal:Tumbleweed - between ## is the new stuff: "The only supported method of repo use for Tumbleweed is to have only the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo active. ## If you use more repositorys you have to know how repo-priorities work, but even then Tumblweed does NOT support this ## " It would also be good to move this information to "Special concerns" and to move the whole "Special concerns"-section up. For example "Special Concerns Virtual Machines ... Third Party Drivers ... ## Non-Standard Repos: Only use Oss, Non-oss, and Update combined with the Tumbleweed-Standard repo. Everything else is not supported and might break the system ## " >You do know the legal reasons behind why packman is there, right? Yes. Then I do not whish you personaly to support Packman with TW - I understand now that this is not possible from your perspectivg. But...as the OS community discusses right now if/how to strengthen Tumbleweed... one way would be, that Packman+TW would be supported BY Packman. So I will ask the Packman-guys to do that... I hope this is possible for them. Without Packman Tumbleweed is so ... "anti-multimedia" ;) thanks anyway :D -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 years, 10 months

[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

7 years, 3 months

[opensuse-factory] YaST2 "install/remove" doesn't display solver diagram

by Kyrill Detinov

Hello. There is a regression in YaST2 *Qt* "install/remove software" module. It doesn't show solver diagram. First, no dependencies on libqdialogsolver. Second, installed libqdialogsolver doesn't help. Reported ages ago. And confirmed. All the info is provided. https://bugzilla.novell.com/show_bug.cgi?id=785431 WBR Kyrill

8 years, 4 months

Re: [opensuse-factory] Nothing provides /usr/bin/php5

by Sascha Peilicke

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

8 years, 4 months

Re: [opensuse-factory] SOLVED: postfix does not run

by Christian Boltz

Hello, Am Freitag, 22. März 2013 schrieb Patrick Shanahan: > /etc/postfix/main.cf had @_some-parameter_@ setting for every > "xxxxxxx_directory =" line. > > After correcting "xxxxxxxx_directory =" settings per my Tumbleweed > machine, postfix appears working correctly. > > This mess probably occurred on installing/upgrading postfix: > postfix-2.9.6-2.1.x86_64 Sun Mar 10 11:14:39 2013 > but the rpm main.cf does not contain "@.............@". This sounds like https://bugzilla.novell.com/show_bug.cgi?id=796162 which should be fixed since some time. I'd guess some older postfix package broke your main.cf. Nevertheless, if you want to be really sure, uninstall postfix, move away /etc/postfix and re-install the postfix package. Regards, Christian Boltz -- Argh, ich wollte heute doch gar nicht mehr siggen! [Michael Hoffmann in dag°] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 years, 6 months

Re: [opensuse-factory] 12.3 RC1 R128 trouble (was: ...install mysteries)

by Felix Miata

On 2013-02-18 16:40 (GMT+0100) Roger Oberholtzer composed: > I am installing 12.3 RC1 on a machine that happily runs earlier versions > of openSUSE. The graphics is, admittedly, an older ATI Rage XL (MACH64). > It runs as a server, and this is on the MB. It is usually only seen > during install. > The install was a bit of a PITA because, no matter what display I used, > I could not get a graphic install to work. I tried setting various > resolutions and even 'No KMS' in the initial install screen. The screen > would go black, and I could do nothing. No virtual terminals. Nothing. > Eventually I had settle for the text install. Using 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Rage Mobility M3 AGP 2x (rev 02) here. 11.4 works OK. I installed HTTP started by Grub using latest factory-snapshot with nomodeset on cmdline. Graphical install worked fine, though slow with only 384M RAM, but resulting X is unusable. The left half of the screen is fine, but the right side is a mess, as if there were some kind of buffer misalignment repeating portions and omitting others. Using nomodeset produces mostly black screens with colored lines in various places at various times in attempting to start the login manager, and kills keyboard. Bunch of Xorg.0.log files: http://fm.no-ip.com/Tmp/Linux/Xorg/os123r128/ Anyone looked for a match to any of these upstream R128 bugs? http://tinyurl.com/bz5lfmv I've commented in the last bug in that list. Exiting X makes the system unresponsive to keyboard and mostly empties the screen to black. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 years, 10 months

[opensuse-factory] Re: What is the purpose of the systemd journal service?

by Linda Walsh

Cristian Rodríguez wrote: > El 15/09/12 11:49, Per Jessen escribió: > >> I do want to log, but I've looked at the journal already and didn't see >> anything that wasn't already in /var/log/messages, /var/log/mail etc. >> Seems like a duplication of effort and a waste of space in >> /var/log/journal. (which afaict can just be deleted). > > It is significantly more powerful than traditional logging: > > For example > > journalctl /usr/bin/foo --> get messages from program foo > > journalctl /dev/sda --> hard-drive problems ? > > journalctl -p error --> only errors > --- I assume the full power of linux's text utilities can be used on them - like grep, sort, awk, perl... vim... Having logs recorded in a non-text binary format tends to make MS logs out-a-sight, out-a-mind, where as I often go and poke around in /var/log and look to see if I notice anything 'new'. If I can't look at the whole stream as a text (messages, warnings, etc), I don't get a field for what is right or wrong behavior and certainly wouldn't be able to pick out an anomaly if I had to query each item separately -- that global view is a good way to look for 'warts'... MS makes it much to painful to do hat -- 1 error / page, everything in 300 separate queries ... ug! > Currently it is not a full replacement for syslog but I suggest you to > check it out. > I tend to use ngsyslog for the filtering benefits. -- really has some powerful filtering in the 2.x line -- had to label ng3x taboo, so it won't overwrite a working config with a non working config... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years

[opensuse-factory] t1lib droppable?

by pgajdos＠suse.cz

Hi list, let us consider removing t1lib from factory. t1lib is unmaintained, see e. g.: CVE-2010-2642 CVE-2011-1552 CVE-2011-1553 CVE-2011-1554 CVE-2011-0433 Packages which requires t1lib for build in factory: evince texlive VFlib3 evince and VFlib3 could perhaps drop --with-t1lib configure switch, texlive could either use its own copy or drop support as well -- it appears from code that it uses t1lib as fallback if freetype2 can't handle given font. Opinions? Do you see any drawbacks? Thanks, Petr

9 years, 1 month

[opensuse-factory] Tumbleweed, future directions

by Greg KH

Hi all. So Tumbleweed is, I think, almost 2 years old now. It seems to be working fairly well, or at least well enough for my daily use, and I haven't heard any complaints about it in a long time which means that either no one is using it, or it's working for others :) Anyway, with the advent of 12.3 soon, I have been thinking if Tumbleweed needed to change any to make things work better. My original set of complaints a year or so ago about OBS issues that keep us having a "proper" rolling distribution, still pretty much are the same: - the build-number issue - build speed - dependancy rebuild problems. Build speed of OBS has increased recently, I don't know if it's just my imagination, or if I have a higher priority for my repos now, or if new hardware really was added to the build system, but I'm happy things seem to be working better in that area at the moment. But the other two issues are still big ones, as the recent GNOME update in Tumbleweed proved quite well. So, I was thinking about maybe, when 12.3 changing Tumbleweed from being an "add-on" repo on top of the 12.3 repos, to being a "full" distro snapshot. That would resolve the build number problems we have had, but the dependancy rebuild issue would increase. The rebuild problem can be manually handled, much like FACTORY currently is, but odds are, I would lean toward the conservative side, having more rebuilds than are probably necessary just to ensure that systems work well. That means that libreoffice would be updated on a weekly basis for users, which might get annoying over time :) Any thoughts by anyone about this? Or should I just do it and see how well it works out? 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, 1 month

[opensuse-factory] after dup fro 12.2 to 12.3 grub menu still 12.2

by Daniele

Hi guys, I'm not a big fun of zypper dup but I did it ! New system is up and running but grub menu still show 12.2 instead of 12.3. Under Yast, boot loader options: Distributor and Default section -> openSUSE 12.2 Is a known issue ? worth a bugreport ? Better way to fix menu entry ? I never touched grub 2 configuration files... Daniele. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 1 month

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory March 2013