to contact Mr Michael Stahnke, the
rubygem-activesupport EPEL branch maintainer. The package needs to be
updated with few fixes.
Thank you.
---
Regards
- P J P
http://feedmug.com
--
Jan Rusnacko, Fedora Security Team
--
devel mailing list
devel@lists.fedoraproject.org
https
from July and we can start working through these -
I`m happy to help you with fix for each of these issues.
Thanks !
--
Jan Rusnacko, Fedora Security Team
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http
of packages
(https://admin.fedoraproject.org/pkgdb/packager/kanarip/), which now have ~20
unfixed vulnerabilities combined in EPEL, some of them for over a year.
Thank you!
--
Jan Rusnacko, Fedora Security Team
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org
On 06.08.2014 16:24, Stephen John Smoogen wrote:
On 6 August 2014 10:53, Jan Rusnacko jrusn...@fedoraproject.org
mailto:jrusn...@fedoraproject.org wrote:
Hello,
following the policy for nonresponsive maintainers, does anyone have a
contact of Jeroen van Meeuwen (kanarip
Hello Thierry,
layout OK.
As for tests - instead of reinventing the wheel by defing class Test_standAlone
to set up instance, use py.test fixture.
Also, you should not force setup, test, teardown execution for each test by
specifying sub-methods for each test. Testing framework (py.test) should
On 10/25/2013 09:36 PM, Jan Rusnacko wrote:
Hello Roberto and Thierry,
as I promised, I am sending you a proof-of-concept code that demonstrates,
how
we can mock DS in unit tests for library function (see attachment). You can
run
tests just by executing py.test in tests directory.
Only
On 10/28/2013 02:52 PM, Roberto Polli wrote:
Hi @all,
Jan wrote:
as I promised, I am sending you a proof-of-concept code that
demonstrates, how we can mock DS in unit tests for library function
Ok, that's clear.
instead of sending command to real DS instance,
they just store the data in
On 10/29/2013 03:30 PM, thierry bordaz wrote:
On 10/29/2013 02:18 PM, Jan Rusnacko wrote:
Hello Thierry,
I am not rewriting ldapadd,... methods of real DS class, I am in fact
creating MockDS class with custom ldapadd,... methods, _just_ like you
suggest :)
Furthermore, you can view
On 10/28/2013 02:31 PM, Rich Megginson wrote:
On 10/26/2013 12:49 AM, Jan Rusnacko wrote:
On 10/25/2013 11:00 PM, Rich Megginson wrote:
On 10/25/2013 01:36 PM, Jan Rusnacko wrote:
Hello Roberto and Thierry,
as I promised, I am sending you a proof-of-concept code that demonstrates,
how
we
On 10/25/2013 11:00 PM, Rich Megginson wrote:
On 10/25/2013 01:36 PM, Jan Rusnacko wrote:
Hello Roberto and Thierry,
as I promised, I am sending you a proof-of-concept code that demonstrates,
how
we can mock DS in unit tests for library function (see attachment). You can
run
tests just
Hello Roberto and Thierry,
as I promised, I am sending you a proof-of-concept code that demonstrates, how
we can mock DS in unit tests for library function (see attachment). You can run
tests just by executing py.test in tests directory.
Only 3 files are of interest here:
https://fedorahosted.org/389/ticket/47558
https://fedorahosted.org/389/attachment/ticket/47558/0001-Initial-commit-with-DSModuleProxy.patch
--
389-devel mailing list
389-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-devel
12 matches
Mail list logo
