search for: patchlevels

Update SuSE Linux detection. Up to now everything with a /etc/SuSE-release file was treated as openSuSE. With this change SLES based distributions such as "SUSE Linux Enterprise Server", "SUSE Linux Enterprise Desktop" and "Novell Linux Desktop" will show up as "sles". The 'opensuse' detection was updated to handle older openSuSE releases as well as

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 ReportedBy:

On Tue, Feb 25, 2020 at 10:59 AM Thomas Zimmermann <tzimmermann at suse.de> wrote: > > Non-KMS drivers store state in struct drm_driver. This bloats the > structure for KMS drivers and prevents it from being declared with > 'static const' qualifiers. Moving the non-KMS state into a separate > data structure resolves this. > > Signed-off-by: Thomas Zimmermann

Dear folks, I'm recently investigating large scale deployment and upgrading FreeBSD RELEASE. 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

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 - EXECUTABLE DIRECTORY: c:/ruby18/bin -

Non-KMS drivers store state in struct drm_driver. This bloats the structure for KMS drivers and prevents it from being declared with 'static const' qualifiers. Moving the non-KMS state into a separate data structure resolves this. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/drm_drv.c | 4 ++++ drivers/gpu/drm/i810/i810_drv.c | 4

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 %>

Allows userspace to detect shared fences are supported. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- drivers/gpu/drm/nouveau/nouveau_drm.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) Dave, can you include this in drm-next? It should allow me to optimize nouveau's vdpau decoding a bit. diff --git a/drivers/gpu/drm/nouveau/nouveau_drm.h

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:

Hi, I run into problems with the ipaddress fact using the latest Facter gem (1.6.4, 1.6.5) 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

I''m submitting this through the mailing list because Trac won''t let me use its bug report form... Is there some more appropriate way of submitting bugs if Trac doesn''t work? This is the Trac error message: 500 Internal Server Error (Submission rejected as potential spam (IP 127.0.0.1 blacklisted by bsb.empty.us, sc.surbl.org, Maximum number of posts per hour for this

# 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: -----------------------------------------------------------

Having a god-awful time installing Rails. I started with the instructions found on this page: http://articles.slicehost.com/2007/11/23/ubuntu-gutsy-mysql-and-ror I get the following error: vbfischer@ubuntu:~$ sudo gem install rails [sudo] password for vbfischer: Bulk updating Gem source index for: http://gems.rubyforge.org/ Updating metadata for 13 gems from http://gems.rubyonrails.org/

I''ve having issues with some part of Mongrel start up process stalling 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)

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

$ gem list wxruby *** LOCAL GEMS *** wxruby (1.9.1, 1.9.0) Ruby interface to the wxWidgets GUI library $ gem install wxruby Need to update 39 gems from 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

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 filesystem (12 x 45 minutes shutdown time). As a result the planned

Hi, I've been trying for the past few days to come up with a method for checking a FreeBSD system to see if it is 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

Hi, I have a couple of FreeBSD-servers that I try to manage using puppet. I''m just trying it out at the moment and have just deployed 5 new boxes (from PXE and scripted installation so supposedly they are all identical except for the name and ip-addresses). On two of the servers I get the error-messages at the bottom of the post. The first error- message I get every time I run puppet on