search for: patchlevel

...SION = 12.2 CODENAME = Mantis ==> Dist/sles8/etc/SuSE-release <== SuSE SLES-8 (AMD64) VERSION = 8.1 ==> Dist/sles9/etc/SuSE-release <== SUSE LINUX Enterprise Server 9 (x86_64) VERSION = 9 ==> Dist/sles9sp2/etc/SuSE-release <== SUSE LINUX Enterprise Server 9 (x86_64) VERSION = 9 PATCHLEVEL = 2 ==> Dist/sles9sp3/etc/SuSE-release <== SUSE LINUX Enterprise Server 9 (x86_64) VERSION = 9 PATCHLEVEL = 3 ==> Dist/sles9sp4/etc/SuSE-release <== SUSE LINUX Enterprise Server 9 (x86_64) VERSION = 9 PATCHLEVEL = 4 ==> Dist/sled10/etc/SuSE-release <== SUSE Linux Enterprise Desk...

https://bugzilla.mindrot.org/show_bug.cgi?id=1640 Summary: Add patchlevel info to the sshd binary. Product: Portable OpenSSH Version: 5.2p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org R...

...er driver = { > .driver_features = DRIVER_USE_AGP | DRIVER_HAVE_DMA | DRIVER_LEGACY, > .dev_priv_size = sizeof(drm_i810_buf_priv_t), > @@ -71,6 +74,7 @@ static struct drm_driver driver = { > .major = DRIVER_MAJOR, > .minor = DRIVER_MINOR, > .patchlevel = DRIVER_PATCHLEVEL, > + .legacy = &i810_legacy_state, > }; > > static struct pci_driver i810_pci_driver = { > diff --git a/drivers/gpu/drm/mga/mga_drv.c b/drivers/gpu/drm/mga/mga_drv.c > index 71128e6f6ae9..4865982d949c 100644 > --- a/drivers/gpu/drm/mga/mga_drv.c...

.... It's our tradition to bump "RELEASE-pN" after a security patch is applied, however, it seems that there is less method to determine whether the userland is patched, which is somewhat important for large site managements. So is "uname -sr" the only way to differencate the patchlevel of a security branch? I have read Colin's freebsd-update script and to my best of knowledge this is the only way (and, on condition that we have re-compiled the kernel and installed it, and reboot'ed). Given the nature of a security or errata branch, we can expect that no API/ABI changes...

Hi, I can''t install Mongrel on Ruby 1.8.6 (patchlevel 279), using Windows XP. My environment: C:\ruby18>gem environment RubyGems Environment: - RUBYGEMS VERSION: 1.2.0 - RUBY VERSION: 1.8.6 (2008-07-17 patchlevel 279) [i386-mingw32] - INSTALLATION DIRECTORY: c:/ruby18/lib/ruby/gems/1.8 - RUBY EXECUTABLE: c:/ruby18/bin/ruby.exe - EXECUTAB...

...cy_state = i810_legacy_state { +}; + static struct drm_driver driver = { .driver_features = DRIVER_USE_AGP | DRIVER_HAVE_DMA | DRIVER_LEGACY, .dev_priv_size = sizeof(drm_i810_buf_priv_t), @@ -71,6 +74,7 @@ static struct drm_driver driver = { .major = DRIVER_MAJOR, .minor = DRIVER_MINOR, .patchlevel = DRIVER_PATCHLEVEL, + .legacy = &i810_legacy_state, }; static struct pci_driver i810_pci_driver = { diff --git a/drivers/gpu/drm/mga/mga_drv.c b/drivers/gpu/drm/mga/mga_drv.c index 71128e6f6ae9..4865982d949c 100644 --- a/drivers/gpu/drm/mga/mga_drv.c +++ b/drivers/gpu/drm/mga/mga_drv.c @@...

I''ve the same problem as Alastair when running rspec command : http://lists.macromates.com/pipermail/textmate/2007-October/022585.html ../spec/mate/runner.rb:34:in `run'': undefined method `parse'' for Spec::Runner::OptionParser:Class I fixed this for me by changing the offending line to : ::Spec::Runner::CommandLine.run(argv, STDERR, stdout) (see

Try this in a view running rails 2.2.3 with ruby 1.8.7. I tried in 1.8.6 and worked just as expected. But in 1.8.7 it doesn''t execute the code inside a condition that has a comment. Sample: <% if (@var)%> @var is nil so it wont get in here <% else # a comment %> it must to get in here, but it doesnt unless the comment in the above condition is removed. <% end %>

...--git a/drivers/gpu/drm/nouveau/nouveau_drm.h b/drivers/gpu/drm/nouveau/nouveau_drm.h index b02b02452c85..8ae36f265fb8 100644 --- a/drivers/gpu/drm/nouveau/nouveau_drm.h +++ b/drivers/gpu/drm/nouveau/nouveau_drm.h @@ -10,7 +10,7 @@ #define DRIVER_MAJOR 1 #define DRIVER_MINOR 2 -#define DRIVER_PATCHLEVEL 0 +#define DRIVER_PATCHLEVEL 1 /* * 1.1.1: @@ -26,6 +26,8 @@ * 1.2.0: * - object api exposed to userspace * - fermi,kepler,maxwell zbc + * 1.2.1: + * - allow concurrent access to bo's mapped read/write. */ #include <nvif/client.h> -- 2.0.4

Hi puppeteers, I have a problem with one of my puppets. When I run puppetd and a file needs to be updated I get the following error message: debug: //jupiter/freebsd_base/File[/etc/rc.conf]: Changing source debug: //jupiter/freebsd_base/File[/etc/rc.conf]: 1 change(s) debug: Calling fileserver.retrieve debug: Calling puppetbucket.addfile err: Could not call puppetbucket.addfile:

...on SLES11. The versions and gems I use work perfectly fine on SLES10 SP3. The problem: running "facter" without arguments results in an error, even though the erroring fact "ipaddress" is ok. test:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 1 test:~ # ruby --version ruby 1.8.7 (2008-08-11 patchlevel 72) [x86_64-linux] test:~ # gem --version 1.3.5 test:~ # puppet --version 2.7.9 test:~ # facter --version 1.6.5 test:~ # facter kernel Linux test:~ # facter ipaddress xx.xx.xxx.xxx (ip address is ok) test:~ # facter The interpreter param...

...that was layered on top of it. Here''s the information on each environment I ran this with: ''''''My local environment'''''': * Linux 2.6.23-gentoo-r6 x86_64 AMD Athlon(tm) 64 Processor 3500+ AuthenticAMD GNU/Linux * ruby 1.8.6 (2008-03-03 patchlevel 114) [x86_64-linux] * ferret (0.11.6) * Results: Test code runs without error. ''''''Remote Server 1'''''': * Linux 2.6.16-xenU SMP i686 GNU/Linux * ruby 1.8.6 (2007-09-23 patchlevel 110) [i686-linux] (compiled from source) * ferret (0.11.6) Re...

# Windows XP Professional + SP3 # ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] # wxruby (1.9.9) If you can tell me how to update to 1.9.10, I''d be happy to run this and a few other tests. Also, if I should be posting bugs somewhere else, please let me know. Here''s a bit of code to reproduce a seg fault: --------------------------------...

...the instructions in this thread: http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/301950cb55487cb5/dd141cfb9563ee42 but none of the suggestions there helped. This is the output from several commands suggested in other threads: vbfischer@ubuntu:~$ ruby -v ruby 1.8.6 (2007-09-24 patchlevel 111) [i486-linux] vbfischer@ubuntu:~$ gem -v 1.1.0 vbfischer@ubuntu:~$ gem environment RubyGems Environment: - RUBYGEMS VERSION: 1.1.0 (1.1.0) - RUBY VERSION: 1.8.6 (2007-09-24 patchlevel 111) [i486-linux] - INSTALLATION DIRECTORY: /usr/lib/ruby/gems/1.8 - RUBY EXECUTABLE: /usr/bin/ruby1....

...with versions of Mongrel greater than 1.1 Using Mongrel Gem version 1.1 both ./script/server and ./merb boot fine But from gem version 1.1.1 both processes stall immediately I can get it to continue by attempting to force quit with CTRL -C system info Mac OS X 10.5.5 Ruby 1.8.7 (2008-05-31 patchlevel 0) [i686-darwin9.5.0] And Mac OS X 10.5.5 Ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9.5.0] Is there a way I can get further information of what is happening in the boot up sequence to investigate further. Thanks -- Anthony Green Client Side Developer Future Media & Technology for...

The beautiful world of uncontained dependencies: - We restrict mockall to 0.11.0, which in practice currently expands to 0.11.4, - mockall depends on predicates-tree, - predicates-tree depends on predicates-core, - approx. two weeks ago, predicates-tree and predicates-core have seen *PATCHLEVEL* upgrades (1.0.7 -> 1.0.9, and 1.0.5 -> 1.0.6, respectively) that now require "rustc 1.64.0 or newer". RHEL-9.2 will eventually ship rustc 1.66, but RHEL-9.2 has not been released. The above rustc requirement bump breaks the nbdkit build on RHEL-9.1 -- which provides rustc 1.62....

...om http://gems.rubyforge.org ....................................... complete Select which gem to install for your platform (i386-mswin32) 1. wxruby 1.9.2 (x86_64-linux) 2. wxruby 1.9.1 (x86_64-linux) 3. Skip this gem 4. Cancel installation > $ gem -v 0.9.2 $ ruby -v ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-mswin32]

Hi, we are using a SLES10 Patchlevel 3 with 12 Nodes hosting tomcat application servers. The cluster was running some time (about 200 days) without problems. Recently we needed to shutdown the cluster for maintenance and experianced very long times for the umount of the filesystem. It took something like 45 minutes each node and file...

...vulnerable to an issue described by a FreeBSD security advisory in some automated way, similar to the way portaudit can use VuXML to check for vulnerabilities in ports. Right now, I'm a bit stuck--there seem to be fairly major issues with all the methods I've come up with: [1] Checking the patchlevel as reported by uname -r. [2] Checking the RCS version tags in the source files listed as changed by the SA [3] Using ident on the binaries affected to extract the RCS tags of the source files used to compile them. [1] Can fail if the user updates through binary patches of the sort offered by fre...

...saction 17215493860 debug: Using cached certificate for ca debug: Using cached certificate for test-db01 debug: OpenSSL: Error(9): certificate is not yet valid debug: OpenSSL: Cert: /CN=deploy01 /usr/local/lib/ruby/site_ruby/1.8/puppet/network/http_pool.rb:68: [BUG] Bus Error ruby 1.8.7 (2009-12-24 patchlevel 248) [amd64-freebsd8] Abort (core dumped) ------------------------------------------------------------------ notice: Starting Puppet client version 2.6.1 debug: Finishing transaction 17215700640 debug: Using cached certificate for ca debug: Using cached certificate for test-db01 debug: OpenSSL: Er...