openSUSE Factory December 2012

factory@lists.opensuse.org

87 participants
90 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

5 years, 7 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

6 years

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

7 years, 1 month

[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

7 years, 9 months

[opensuse-factory] rpmlint: warn if -ansi is used to build packages

by Cristian Rodríguez

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

7 years, 11 months

[opensuse-factory] Re: Fontconfig fonts priority

by Lars Müller

On Wed, Feb 01, 2012 at 12:22:50PM +0100, Mariusz Fik wrote: > Dnia środa, 1 lutego 2012 01:03:13 Sven Burmeister pisze: > > Am Dienstag, 31. Januar 2012, 22:43:11 schrieb Mariusz Fik: > > > > > > current fontconfig configuration[1] sets the highest priority for > > > Microsoft font. If user install them (i.e. Times New Roman, Arial, > > > Consolas) they will be set as _default_ for respectively families > > > (sans-serif, sans, monospace). Why do we promote Microsoft fonts > > > instead support open fonts, shipped with system? > > > > > > I propose[2] to downgrade those fonts. Thanks to this, we keep our > > > default font settings but those MS fonts will be still available for > > > use. > > > > > > Whats Your point of view in this case? > > > > Are you sure that the free fonts have the same quality – even if > > anti-aliasing is disabled? I remember ugly characters with free fonts > > unless I would use bitmap fonts and that's a no-go IMHO. My suggestion is: > > Set the best quality fonts as default. Those that do not want to use MS > > fonts simply do not install them. There was a reason to prefer those fonts > > and AFAIR it was quality or lack thereof regarding the free fonts. > > The goal is: to not set those fonts as _default_ and not to get them rid off . > Why Joe when install i.e. Consolas font should get it set as default monospace > font? Maybe he want's only to use it in a single program? Please continue this thread at opensuse-factory as it was already suggested as part of this thread. Therefore the Reply-To got set. The begin of this thread was here: http://lists.opensuse.org/opensuse/2012-01/msg02101.html Why? Cause it's more likely that you'll get the required attention. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

8 years

[opensuse-factory] Maintainer model clean up

by Robert Schweikert

Hi, This is also related to the "Coolo needs help thread". During osc12 we had various discussions related to the topic of getting the distribution out the door and how we can get there within the release schedule that we had agreed to a while back. Part of this discussion are the two sessions I had the opportunity to lead, both are available on youtube opensusetv, if you are interested in this topic please go and watch these sessions, as well as Stephan's session, also on youtube. Unfortunately we did not have video equipment in the BoF session. The basic proposal is, and this received general agreement at osc12, that we will move toward changing the model as proposed in the session. This implies the following: - In the web UI one will no longer see inherited project maintainers on the package page, only the "true" package maintainers. (Inherited "maintainers" will be hidden in an expandable tree) - We will collect information about all packages in all devel projects that feed factory. We will generate a list of packages that have no maintainer, and a list of packages that need help, i.e. a package that has fewer than 5 maintainers. In addition we will list packages that have more than 5 maintainers and try to encourage maintainers from those packages (to get the number to 5) to take on packages that need help. - We want to clean up the devel project maintainer list to a ratio of 10/500 packages with a max of 25. ~ In many cases package maintainers in a given project do not care about all the other packages in the project, yet they are on the project maintainer list. ~ Also many people have their Hermes notifications disabled as they get too many messages about packages they do not care, hopefully with the changes more people will re-enable their Hermes notifications (more on this below) - We would like to see a notification on the package page if the package fails to build in factory - Would like to see package build status information on the factory status page about the status of the package in it's devel project. - Having the monitor page and the status page presented in the current form is confusing, we need to somehow merge the information. - It would be really nice if there were some kind of policy engine that could enforce the "no more than 5 per package" and the "no more than 25 project maintainers" policies. ~ now OBS is not just for openSUSE, thus this cannot be hard coded into the OBS code, thus this is potentially a lot of work. - We would like to have some kind of rating system on the devel projects - We will produce guidelines for package and product maintainers outlining what is expected. ~ These guidelines are not hard rules, but provide help to new people stepping in to define the role they are comfortable with. There appears to be a problem that the complete void of guidelines in this area leads to paralysis and people just do not know what to do if they want to help. We have documents how to package, these guidelines will be a hopefully short list of "what is expected". These are the rough outlines of the "plan". Obviously there is work to be done and the OBS team already has plenty to do. It is up to me to document in more detail the requirements/use case before a potential timeline can be developed. I will also start a wiki page attempting to define the various roles in the devel process and then opening that up for discussion once the basics are in place. Now to a couple of counter points. - Yes we will step on some people's toe, sorry. Meaning if you get removed as project maintainer from a devel project and you really really want to be a project maintainer you are probably not going to be happy. Please do not take it personal and get yourself added back to the project. Preferably you would find one of the project maintainers that remained, by chance and chance alone, and get that person to drop of the list. Chances are you will find someone willing to "make space for you" ~ Sorry, but this process has to be somewhat arbitrary due to the large number on the various devel projects. ~ Please be not offended, there is no vicious intent, just the intent to help the project grow and scale better. - Yes, the "rules" are changing, and if you maintain a package that is also in factory there will now be some expectations ~ In the end we all should have the same goal, create a quality distro in the time frame we promise, thus this should really not be a big deal Before I close this rather long e-mail (sorry) I have a kind of survey question. I would like to have the hermes settings of package maintainers reset "automatically" as we move through the house keeping project such that package maintainers get notification of build failures of their packages. I realize many people have these turned off today, but again, this is probably due to the number of notifications due to the project maintainer mails that most people do not care about. OK, before I write another couple of pages about this subject I'll stop here. Thanks for your attention, please no flaming, bitching and moaning. Great ideas and help are welcome. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 years, 1 month

Re: [opensuse-factory] Cursed intel graphics card, freezes desktop at random. Tried 3 different kernels

by Roger Luedecke

On Thu, 2012-12-27 at 17:11 -0500, Felix Miata wrote: > Respond back to list if you want. > > On 2012-12-27 13:56 (GMT-0800) Roger Luedecke composed: > > > On Thu, 2012-12-27 at 15:49 -0500, Felix Miata wrote: > > >> On 2012-12-27 11:54 (GMT-0800) Roger Luedecke composed: > > >> > On Thu, 2012-12-27 at 14:24 -0500, Felix Miata wrote: > > >> >> Does it help to put http://fm.no-ip.com/Tmp/Linux/Xorg/70-composite.conf in > >> >> /etc/X11/xorg.conf.d/ ? > > >> > Going to apply this now, and will reboot and pray. > > >> Rebooting is for new kernels and for Windows. Restarting GDM is all you need > >> to implement that config file. > > > SO that is GDM specific then. > > _What_ is GDM specific? xorg.conf.d/ content is global X, regardless of DE. > What you did previously was probably as most troubleshooters do, to disable > bling only in the user environment via a personal setting, leaving it running > at the GDM level. With composite disabled globally there could be an > important functional difference from only disabling it personally. > > > Either way, so far so stable. But, this > > newer kernel plays a little nicer than the 12.2 stock kernel. Yeah, I set it to force fallback mode. Still froze though. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 years, 1 month

[opensuse-factory] gtkglext missing from factory

by Josef Reidinger

Hi, some project in games repository start failing as opensuse:Factory doesn't have gtkglext. Is it intention? I found that it is in 12.2 and cannot find in in opensuse:DROPPED. It is accident or intention? Thanks for answer Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 years, 1 month

[opensuse-factory] Wiki does not provide repos for testing factory

by Patrick Shanahan

Isn't the repos necessary to test factory one bit of information that should be provided on the factory wiki page? http://en.opensuse.org/Portal:Factory -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 years, 1 month

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory December 2012