search for: inconstancy

Hi. I've found inconstancy between output of repoquery and rpm. I was looking forward towards apache php 5.4 module which must provided by some package SCL (can someone tell me?). rpm -qf /etc/httpd/modules/mod_proxy.so httpd-2.2.15-29.el6.centos.x86_64 repoquery -qf /etc/httpd/modules/mod_proxy.so so repoquery results i...

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=505 kaber@trash.net changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|laforge@netfilter.org |pablo@netfilter.org Version|CVS (please indicate |1.1.2 ------- Additional Comments From kaber@trash.net

I keep running into errors on the i686-mingw32-RA-on-linux bot and was curious if someone could test a patch against the bot or something with a similar setup. I believe it should now work properly, but would like to make sure that it'll pass before possibly adding a third commit/revert cycle. If the history isn't an issue, let me know an I'll just keep trying. The differential is

I think median() behaves as designed: As long as the argument can be ordered, the "middle observation" makes sense, except when the middle falls between two categories, and you can't define and average of the two candidates for a median. The "sick man" would seem to be var(). Notice that it is also inconsistent with cov(): >

Hello, Is there a reason for the following behaviour? > mean(c("1","2","3")) [1] NA Warning message: In mean.default(c("1", "2", "3")) : l'argument n'est ni num?rique, ni logique : renvoi de NA But: > var(c("1","2","3")) [1] 1 And also: >

Jean-Luc, Please keep the communications on the list, for the benefit of others, now and in the future, via the list archive. I am adding r-devel back here. I can't speak to the rationale in some of these cases. As I noted, it may be (is likely) due to differing authors over time, and there may have been relevant use cases at the time that the code was written, resulting in the various

Hi, Martin! You can find pretty nice instructions how to do it via Phabricator here: http://llvm.org/docs/Phabricator.html. -Maxim On 23/02/16 21:30, Xinliang David Li via llvm-dev wrote: > Can you send this patch to llvm-commits ? > > David > > On Tue, Feb 23, 2016 at 1:15 AM, Martin Liška <llvm-dev at lists.llvm.org > <mailto:llvm-dev at lists.llvm.org>> wrote:

Ok, this one actually produces the message I intended... Questions for the community and team: 1) should warnings be at DEBUG(2, and notices at 3? 2) should errors like "path points to non-dir" cause a fatal error as well as an error message? 3) should the share names be in []s in the messages? --dave -------------- next part -------------- 1770c1770,1772 < incomplete or

I've been unhappy for some time with the weak checking of service self-consistency in .../source/param/loadparm.c's "service_ok" function. Here's my initial draft of a better one, in diff format. Suggestions and criticism welcome! --dave -- David Collier-Brown, | Always do right. This will gratify 185 Ellerslie Ave., | some people and astonish the rest. Willowdale,

Has one try to install the ggplot2 package recently? I tried to install it on my new system and had trouble: > install.packages("ggplot2") Installing package(s) into 'C:/Program Files/R/R-2.14.2/library' (as 'lib' is unspecified) also installing the dependency 'scales' trying URL