February 2013 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] repository priorities with Tumbleweed
by Thomas Langkamp 16 Jul '15

16 Jul '15

> 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

11 18

[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

[opensuse-factory] YaST2 "install/remove" doesn't display solver diagram
by Kyrill Detinov 13 Jan '14

13 Jan '14

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

3 3

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

Re: [opensuse-factory] 12.3 RC1 R128 trouble (was: ...install mysteries)
by Felix Miata 12 Jul '13

12 Jul '13

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

2 2

[opensuse-factory] Re: What is the purpose of the systemd journal service?
by Linda Walsh 14 May '13

14 May '13

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

27 129

[opensuse-factory] Tumbleweed, future directions
by Greg KH 10 Apr '13

10 Apr '13

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

15 24

[opensuse-factory] rpmlint: warn if -ansi is used to build packages
by Cristian Rodríguez 19 Mar '13

19 Mar '13

Hi: Will be cool if rpmlint could warn when upstream packages attempt to use the -ansi gcc option because it inhibits usage of gcc builtin functions while optimizing (list here --> http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html#Other-Builtins) most recently it caught my attention that it also disables the new "optimize-strlen" pass in gcc 4.7, in particular this: "for hosted compilations where stpcpy is available in the runtime and headers provide its prototype, e.g. void foo (char *a, const char *b, const char *c, const char *d) { strcpy (a, b); strcat (a, c); strcat (a, d); } can be optimized into: void foo (char *a, const char *b, const char *c, const char *d) { strcpy (stpcpy (stpcpy (a, b), c), d); } " when -ansi is used and (defined(_GNU_SOURCE) || (_XOPEN_SOURCE >= 700 || _POSIX_C_SOURCE >= 200809L)) is false, there is no stpcpy prototype and hence no optimization. Thoughts ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 28

[opensuse-factory] Tumbleweed: NV34 card scrmables colors after update
by Achim Gratz 17 Mar '13

17 Mar '13

I have an old computer with an FX5200 AGP card. I've tried to update it this weekend to the latest Tumbleweed and the colors in X are all scrambled. Only the colors are wrong and it looks like the order of the bits is reversed or something: the tinier the expected color variation, the more drastic the actual result. I can't find any parameter that seems to influence that and searching the bugbase has also come up empty. Does somebody has an idea of what to try? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 5

[opensuse-factory] Network Stack in 12.3
by Dimstar / Dominique Leuenberger 03 Mar '13

03 Mar '13

Hi all, As many are surely aware, there are 'funny' issues in 12.3 when it comes to the network stack. On my machine, I experienced WiFi not being able to connect at all (Intel chip). => Updating the kernel-firmware package (Used Larry's pkg!) worked around this.. Then, NetworkManager and sysconfig seem to cause real pain. sysconfig was updated to 0.80.x (and a respective change added to NM). Now, whenever I use this configuration (tested on cable/LAN), then there is either no default route set, or /etc/resolv.conf is not being written. Having my system back in shape by reverting to sysconfig 0.76.8 and reverting NM to not make use of sysconfig 0.8 features got me running again. Don't get me wrong: I don't say we should kill the progress of sysconfig, but we should postpone this for 13.1, as in my opinion we are way to late in the release to figure out what all goes wrong and needs fixing (the issue is larger than it looks at first, just look at issues caused by this like https://bugzilla.novell.com/show_bug.cgi?id=804052, where yast does not know how to perform the switch anymore between ifup and NM. As such, I very much vote for - Inclusion of kernel-firmware update, as prepared by Larry - Revert sysconfig to 0.78.8 - Revert the change in NetworkManager ( https://build.opensuse.org/package/rdiff?linkrev=base&package=NetworkManage… ) NOTE: Even doing this revert will leave machines which HAD these packages in a 'weird' state: NETWORKMANAGER=yes/no was removed from /etc/sysconfig/network/config with sysconfig 0.80 and rolling back to 0.78.8 adds =no to the system. So those machines might be in a very odd stage... yet, this is a 'rather' small subset of systems which we can possibly manage. Looking forward to some noise here! Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1