similar to: newest up2date rpm

Displaying 20 results from an estimated 300 matches similar to: "newest up2date rpm"

2005 Oct 28
0
up2date error
I am getting the follinf error with u2date: # up2date -l Fetching Obsoletes list for channel: centos4-Base... Fetching obsoletes list for http://mirror.centos.org/centos/4/os/x86_64/... ####################################### Fetching Obsoletes list for channel: centos4-Updates... Fetching obsoletes list for http://mirror.centos.org/centos/4/updates/x86_64/...
2006 Mar 14
1
Using up2date to download channels on rhn
Hi all, i have a problem with centos's up2date tool. I have setup a central update server with yam (http://dag.wieers.com/home-made/yam/) under CentOS-4. When yam calls t up2date to download updates, up2date returns this error: Traceback (most recent call last): File "/usr/bin/yam", line 1099, in ? main() File "/usr/bin/yam", line 983, in main
2006 Aug 08
1
i386 and x86_64 depsolver issue with Seamonkey
CentOS uses the yum dependency solver for doing updates and not the RHN (normal) up2date mechanism. That is functionality built into up2date. Due to this difference, there is a problem with the Seamonkey upgrade to replace Mozilla using up2date on CentOS-4, because it does not see Seamonkey as obsoleting Mozilla. (This is a problem with the yum depsolver that is included in up2date). Due to
2013 Apr 02
1
R doesn't recognize utils functions, such as arrayIndex( )
Hi all, When I called arrayIndex(20:23, dim=c(4,3,3)), it says "Error: could not find function "arrayIndex"in R". So I called ls("package:utils") to see the functions inside: [1] "?" [2] "adist" [3] "alarm" [4] "apropos" [5] "aregexec" [6] "argsAnywhere" [7] "arrangeWindows" [8]
2010 Dec 02
1
parLapply - Error in do.call("fun", lapply(args, enquote)) : could not find function "fun"
Hello everybody, I've got a bit of a problem with parLapply that's left me scratching my head today. I've tried this in R 2.11 and the 23 bit Revolution R Enterprise and gotten the same result, OS in question is Windows XP, the package involved is the snow package. I've got a list of 20 rain/no rain (1/0) situations for these two stations i and j, all the items in this list look
2007 Oct 06
3
Prototype: resp.getHeader('Location'); redirects browser
Why when I call resp.getHeader(''Location''); after my ajax call does the browser get redirected to the location header. I just want to get the value of it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to
2012 Feb 08
2
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Hello, I'm finding problems with BackEdgeTaken count calculation in even simple fortran loops with gfortran-4.6 + DragonEgg 3.0. Even for simple double loops like this one: program test2 integer i,j,k dimension k(100,100) do j=1,100 do i=1,100 k(i,j) = i enddo enddo write(*,*) k(1,30) end make the ScalarEvolution
2012 Feb 08
2
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Attached 2012/2/8 Marcello Maggioni <hayarms at gmail.com>: > Mmm, sorry, the patch I posted crashes if ExitBr is null (which it may > be ...) , this one should be ok (and passess all the ScalarEvolution > tests in LLVM): > > diff --git a/lib/Analysis/ScalarEvolution.cpp b/lib/Analysis/ScalarEvolution.cpp > index daf7742..b10fab2 100644 > ---
2012 Feb 08
0
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Mmm, sorry, the patch I posted crashes if ExitBr is null (which it may be ...) , this one should be ok (and passess all the ScalarEvolution tests in LLVM): diff --git a/lib/Analysis/ScalarEvolution.cpp b/lib/Analysis/ScalarEvolution.cpp index daf7742..b10fab2 100644 --- a/lib/Analysis/ScalarEvolution.cpp +++ b/lib/Analysis/ScalarEvolution.cpp @@ -4293,9 +4293,15 @@
2012 Feb 08
2
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Well, it wasn't intended as a "real" patch to be included , but more as a "proof of concept" for a solution. Do you think it is a valid solution and I'm correct in my assumption? If so then I'll clean up the patch and attach a testcase for inclusion. Thanks! Marcello 2012/2/9 Nick Lewycky <nlewycky at google.com>: > Your patch should include a testcase,
2012 Feb 08
0
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
Your patch should include a testcase, see test/Analysis/ScalarEvolution for examples. "BranchInst* " should be "BranchInst *". You should have spaces after the // in your comments. One of the comment lines isn't indented properly. Nick On 8 February 2012 12:05, Marcello Maggioni <hayarms at gmail.com> wrote: > Attached > > 2012/2/8 Marcello Maggioni
2012 Feb 09
2
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
This is the .ll for that graph (attached). I think I understand what you are saying. This particular testcase returns CNC not because the exit block doesn't have a unique predecessor, but because the unique predecessor (the inner loop block) has a successor that is inside the loop (in this case itself, because it's the inner loop block). That doesn't change, anyway, the assuption that
2012 Feb 08
0
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
On 8 February 2012 15:50, Marcello Maggioni <hayarms at gmail.com> wrote: > Well, it wasn't intended as a "real" patch to be included , but more > as a "proof of concept" for a solution. Do you think it is a valid > solution and I'm correct in my assumption? If so then I'll clean up > the patch and attach a testcase for inclusion. > I'm
2012 Feb 09
0
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
This is instead a very simple (handmade) test case that triggers the problem (attached) Also a more conforming patch has been attached 2012/2/9 Marcello Maggioni <hayarms at gmail.com>: > This is the .ll for that graph (attached). I think I understand what > you are saying. > This particular testcase returns CNC not because the exit block > doesn't have a unique predecessor,
2012 Feb 09
1
[LLVMdev] BackedgeTakenCount calculation for fortran loops and DragonEgg gfortran-4.6
FInally I had the time to complete everything up. Now I included the test case in the patch and the testcase runs with the LLVM tests system. 2012/2/9 Marcello Maggioni <hayarms at gmail.com>: > This is instead a very simple (handmade) test case that triggers the > problem (attached) > Also a more conforming patch has been attached > > 2012/2/9 Marcello Maggioni <hayarms
2005 Oct 28
0
Yum/Update anomolies: not a problem?
Today, got a wild hair and decided to check the update logs. I don't know why I want to destroy my perfectly reasonable sense of complacency at my advanced age... OOPS! Humor, sorry, retracted. Anyway, after googling and reading about half the posts related to the two sets of messages below, I have reached the tentative conclusion that this is not a major problem. Is this assessment correct?
2007 Jan 30
2
Can up2date use a local yum mirror?
If so, how do you configure the up2date client that comes with CentOS to look at the local yum mirror? Conversely, how do you disable the CentOS Network Alert Notification Tool so that users won't see the "throbbing red circle" and be tempted to launch the up2date client? Thanks, Alfred
2008 Jan 20
1
Up2date
Hi all, I want to use UP2DATE to alert me to updates that are available but still use yum to make the update. Up2date alerts me and i see what is available and then update with yum. Up2date icon still shows updates are available. How can I get up2date to know that the system has been updated? Thank you. -- Regards Robert Smile... it increases your face value! Linux User #296285
2006 Sep 01
0
CEBA-2006:0901 Important CentOS 4 i386 up2date - bugfix update
CentOS Errata and Bugfix Advisory 2006:0901-001 The up2date released with CentOS-4.4 did not specifically require the new centos-release, however the new centos-release provides the /etc/sysconfig/rhn/sources file for up2date. This update changes up2date to require centos-release >= 4-4.2 which will allow up2date to be used to upgrade of CentOS from 4.3 (or older versions) to 4.4. The
2006 Sep 01
0
CEBA-2006:0901-001 Important CentOS 4 x86_64 up2date - bugfix update
CentOS Errata and Bugfix Advisory 2006:0901-001 The up2date released with CentOS-4.4 did not specifically require the new centos-release, however the new centos-release provides the /etc/sysconfig/rhn/sources file for up2date. This update changes up2date to require centos-release >= 4-4.2 which will allow up2date to be used to upgrade of CentOS from 4.3 (or older versions) to 4.4. The