similar to: Koji/CBS infra and sslv3/Poodle important notification

Displaying 20 results from an estimated 200 matches similar to: "Koji/CBS infra and sslv3/Poodle important notification"

2014 Oct 15
0
CentOS-announce Digest, Vol 116, Issue 8
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2015 Jan 06
0
Infra - CentOS hardware move [cbs]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Due to a hardware move (machines needing to be powered off, moved in another rack) , some CentOS.org services will be unreachable for a short period of time. Impacted services : * cbs/Community Build System (aka http://cbs.centos.org) Koji web/hub and builders will be down Migration is scheduled for Thursday January 8th, 3:00 pm UTC time. You can
2007 Sep 30
2
Initial setup problems on Ubuntu edgy (06.10)
Good day, After having lurked for a while I''ve decided to actually start using puppet starting on my small home network. I''ve been following : http://reductivelabs.com/trac/puppet/wiki/InstallationGuide and :- http://www.howtoforge.com/installing_puppet_on_ubuntu to test puppet on 2 hosts, librarian running the puppetmasterd and mortvm. Unfortunately, I
2011 Mar 01
1
does rpy support R 2.12.2
Hi, I am getting the following error when I try to run import rpy from the the python IDE: Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.6/dist-packages/rpy.py", line 134, in <module> """ % RVERSION) RuntimeError: No module named _rpy2122 RPy module can not be imported. Please
2009 Jul 09
1
Rpy not working after upgrade to R2.9.1
Hi, I'm running Ubuntu Jaunty, downloading R and Rpy from this repository: deb http://cran.uk.r-project.org/bin/linux/ubuntu jaunty/ When was automatically upgraded, Rpy (which should be downloaded from the same repository) seems to have stopped working. I've tried re-installing the python-rpy package manually. I get the following error when I try to import rpy: >>> import
2009 Jan 09
1
Calling R functions from Python
All- Thanks in advance for your help. I'm trying to call R function using Python in a windows environment and have downloaded the Rpy library however it doesn't appear to work with R 2.7.2. Does anyone know if a new version of Rpy exists for windows that will work with R and where it can be downloaded from? Here's an example of the error I'm getting:
2008 Mar 24
1
Running rpy produces the error message undefined symbol: KillAllDevices
Hello All, I've been using R for a while and decided to test R from the svn trunk. I know that trunk is not stable, but I wanted to see if I can install and run the latest rpy on my Ubuntu 7.10 box. It installed ok, but I got the runtime error message: $ python Python 2.5.1 (r251:54863, Mar 7 2008, 04:10:12) [GCC 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)] on linux2 Type
2012 Jul 17
1
python-rpy DEB broken - but hopefully easy to fix
Hi CRAN people, There is an issue with python-rpy on Ubuntu, when installed from the CRAN repository. (I read the info on http://cran.r-project.org/bin/linux/ubuntu/ and saw the note that this package is experimental but you are happy to receive feedback on it.) After adding the appropriate CRAN repo: % sudo apt-get install python-rpy [ ... installs various dependencies ... ] % echo import rpy |
2009 Sep 21
0
Ubuntu Hardy python-rpy package missing _rpy2092 (PR#13962)
Full_Name: Dennis Ristuccia Version: R version 2.9.2 (2009-08-24) OS: Ubuntu Hardy 8.04 Submission from: (NULL) (18.157.249.21) Hi guys, I'm running into an issue with the python-rpy ubuntu hardy package. Heres the output: root at tak ~# python Python 2.5.2 (r252:60911, Jul 22 2009, 15:35:03) [GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu3)] on linux2 Type "help", "copyright",
2011 Mar 12
0
try with succes rpm bind 9.7.3 with koji el4 and el5
rehello centos list after some modifications rpm fedora core 14 of bind-9.7.3 and patching. diff -u unpatched/configure.in patched/configure.in --- unpatched/configure.in 2010-07-05 14:02:20.000000000 +0200 +++ patched/configure.in 2010-07-05 14:03:48.000000000 +0200 @@ -282,7 +282,8 @@ AC_C_INLINE AC_C_VOLATILE AC_CHECK_FUNC(sysctlbyname, AC_DEFINE(HAVE_SYSCTLBYNAME))
2009 Jul 15
0
Weird build bug in Koji / EL-5 (can anyone help?)
Compare this successful build of 1.0.60 in EPEL-5: http://kojipkgs.fedoraproject.org/packages/libguestfs/1.0.60/2.el5/data/logs/x86_64/build.log with this unsuccessful build of 1.0.61, done ~24 hours later: http://koji.fedoraproject.org/koji/getfile?taskID=1477023&name=build.log The unsuccessful build fails with: /usr/lib/rpm/debugedit: canonicalization unexpectedly shrank by one
2020 Jul 31
0
Re: nbdkit build failure in Koji
On 7/31/20 7:07 AM, Richard W.M. Jones wrote: > Hi Eric, > > I wonder if you have any thoughts about this build failure in > tests/test-nozero.sh? > > https://koji.fedoraproject.org/koji/taskinfo?taskID=48259627 > log: https://kojipkgs.fedoraproject.org//work/tasks/9762/48259762/build.log > > The error is “nozero6.img was trimmed by mistake”. I added “set -x”
2020 Aug 01
0
Re: nbdkit build failure in Koji
On Sat, Aug 01, 2020 at 08:46:11AM +0100, Richard W.M. Jones wrote: > > One thing I noticed which is a bit odd is: > > $ rm file; for f in {0..1023}; do printf '%1024s' .; done > file; stat -c "%b %B" file > 2048 512 > $ rm file; for f in {0..1023}; do printf '%1024s' . >> file; done ; stat -c "%b %B" file > 3968 512 > >
2020 Aug 03
0
Re: nbdkit build failure in Koji
On Mon, Aug 03, 2020 at 04:21:13PM -0500, Eric Blake wrote: > On 8/1/20 12:39 PM, Richard W.M. Jones wrote: > >On Sat, Aug 01, 2020 at 08:46:11AM +0100, Richard W.M. Jones wrote: > >> > >>One thing I noticed which is a bit odd is: > >> > >>$ rm file; for f in {0..1023}; do printf '%1024s' .; done > file; stat -c "%b %B" file >
2017 Jan 20
1
koji in extras older than epel
Now that EPEL 7 has koji-1.11, should the one in CentOS 7 extras be updated or removed?
2014 Oct 16
1
POODLE on CentOS
The following updates address POODLE on CentOS: CentOS-5: http://lists.centos.org/pipermail/centos-announce/2014-October/020696.html CentOS-6.5: http://lists.centos.org/pipermail/centos-announce/2014-October/020697.html CentOS-7: http://lists.centos.org/pipermail/centos-announce/2014-October/020695.html Please note that the CentOS-6.5 updates are built from: openssl-1.0.1e-30.el6_5.2.src.rpm
2015 Jul 08
0
Samba 4 - disabling SSLv3 to mitigate POODLE effects
I have file a bug and modified the source code to make samba4 do not use SSLV3, but I am not able to make a patch to this. https://bugzilla.samba.org/show_bug.cgi?id=11076 -----Original Message----- From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Mario Pio Russo Sent: Wednesday, July 08, 2015 4:48 PM To: samba at lists.samba.org Subject: [Samba] Samba
2014 Oct 19
3
Dovecote 1.2.17 poodle
Hi, how do I protect dovecot 1.2.17 against poodle? Br /Marc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: Message signed with OpenPGP using GPGMail URL: <http://dovecot.org/pipermail/dovecot/attachments/20141019/b4152487/attachment-0001.sig>
2014 Oct 17
1
POODLE and TLSv1
I read this on the RHN commentary respecting cve-2014-3566: https://securityblog.redhat.com/2014/10/15/poodle-a-ssl3-vulnerability-cve-2014-3566/: . . . The first aspect of POODLE, the SSL 3.0 protocol vulnerability, has already been fixed through iterative protocol improvements, leading to the current TLS version, 1.2. It is simply not possible to address this in the context of the SSL 3.0
2014 Nov 04
2
Samba 4 - disabling SSLv3 to mitigate POODLE effects
Hi all, Am trying to find a way to disable SSLv3 protocol in smb.conf on Samba4. I am using the following: tls enabled = yes tls keyfile = tls/myKey.pem tls certfile = tls/myCert.pem tls cafile = With a self-signed cert. But when I remote connect from another host using: openssl s_client -showcerts -connect samba4-dc:636 -ssl3 I get a successful