Hi
I hope to participate in Outreachy 2017 under Fedora in the project 389 Directory, mentored by William Brown. I am fluent with the skills mentioned for the project. How should I start the application process and my contributions to be a strong candidate for this project.
Gratitude.
On Tue, 2017-09-26 at 11:20 +0530, Dristi Butola wrote:
Hi
I hope to participate in Outreachy 2017 under Fedora in the project 389 Directory, mentored by William Brown. I am fluent with the skills mentioned for the project. How should I start the application process and my contributions to be a strong candidate for this project.
Hi there,
Thanks for your interest! I'm still looking through everyone who has shown an interest in the project, and I have been sick recently so I'm really sorry for the late response :(
I think the best place to start is our contributing guide. It says how you can setup the server and source, and start looking at it.
http://www.port389.org/docs/389ds/contributing.html
I hope that this gives you a place to start asking questions,
Hello :) I facing an issue while building it locally, although `yum install 389-ds-base` worked fine but when I try to build the server locally by referencing http://www.port389.org/docs/389ds/contributing.html , this command `$ sudo dnf builddep --setopt=strict=False 389-ds-base/rpm/ 389-ds-base.spec.in` , gives me an ERROR "no package matched: 389-ds-base/rpm/389-ds-base.spec.in".
On Thu, Sep 28, 2017 at 4:29 AM, William Brown wibrown@redhat.com wrote:
On Tue, 2017-09-26 at 11:20 +0530, Dristi Butola wrote:
Hi
I hope to participate in Outreachy 2017 under Fedora in the project 389 Directory, mentored by William Brown. I am fluent with the skills mentioned for the project. How should I start the application process and my contributions to be a strong candidate for this project.
Hi there,
Thanks for your interest! I'm still looking through everyone who has shown an interest in the project, and I have been sick recently so I'm really sorry for the late response :(
I think the best place to start is our contributing guide. It says how you can setup the server and source, and start looking at it.
http://www.port389.org/docs/389ds/contributing.html
I hope that this gives you a place to start asking questions,
-- Sincerely,
William Brown Software Engineer Red Hat, Australia/Brisbane
389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
On Fri, 2017-09-29 at 15:50 +0530, Dristi Butola wrote:
Hello :) I facing an issue while building it locally, although `yum install 389-ds-base` worked fine but when I try to build the server locally by referencing http://www.port389.org/docs/389ds/contributing.html , this command `$ sudo dnf builddep --setopt=strict=False 389-ds-base/rpm/ 389-ds-base.spec.in` , gives me an ERROR "no package matched: 389-ds-base/rpm/389-ds-base.spec.in".
I think there is a mistake on the page, there is a $$2 where it should be $2
sudo dnf install --setopt=strict=False `grep -E "^(Build)?Requires" ds/rpm/389-ds-base.spec.in lib389/python-lib389.spec | grep -v -E '(name|MODULE)' | awk '{ print $$2 }' | sed 's/%{python3_pkgversion}/3/g' | grep -v "^/" | grep -v pkgversion | sort | uniq | tr '\n' ' '`
^ Has the error, see the awk command? Should be:
awk '{ print $2 }'
I think as well perhaps:
ds/rpm/389-ds-base.spec.in
Should be:
389-ds-base/rpm/389-ds-base.spec.in
Try changing those and see how it goes,
Hi :)
I am facing the problem in the command just above the command you pointed have an error.
sudo dnf builddep --setopt=strict=False 389-ds-base/rpm/389-ds-base.spec.in
it gives me this error
no package matched: 389-ds-base/rpm/389-ds-base.spec.in.
How to solve this ?
Thanks.
On Sat, Sep 30, 2017 at 5:38 AM, William Brown wibrown@redhat.com wrote:
On Fri, 2017-09-29 at 15:50 +0530, Dristi Butola wrote:
Hello :) I facing an issue while building it locally, although `yum
install
389-ds-base` worked fine but when I try to build the server locally by referencing http://www.port389.org/docs/389ds/contributing.html , this command `$ sudo dnf builddep --setopt=strict=False 389-ds-base/rpm/ 389-ds-base.spec.in` , gives me an ERROR "no package matched: 389-ds-base/rpm/389-ds-base.spec.in".
I think there is a mistake on the page, there is a $$2 where it should be $2
sudo dnf install --setopt=strict=False `grep -E "^(Build)?Requires" ds/rpm/389-ds-base.spec.in lib389/python-lib389.spec | grep -v -E '(name|MODULE)' | awk '{ print $$2 }' | sed 's/%{python3_pkgversion}/3/g' | grep -v "^/" | grep -v pkgversion | sort | uniq | tr '\n' ' '`
^ Has the error, see the awk command? Should be:
awk '{ print $2 }'
I think as well perhaps:
ds/rpm/389-ds-base.spec.in
Should be:
389-ds-base/rpm/389-ds-base.spec.in
Try changing those and see how it goes,
-- Sincerely,
William Brown Software Engineer Red Hat, Australia/Brisbane
389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
On Sat, 2017-09-30 at 16:46 +0530, Dristi Butola wrote:
Hi :)
I am facing the problem in the command just above the command you pointed have an error.
sudo dnf builddep --setopt=strict=False 389-ds-base/rpm/389-ds-base.spec.in
it gives me this error
no package matched: 389-ds-base/rpm/389-ds-base.spec.in.
How to solve this ?
Thanks.
According to my own notes I don't even use that command. I think it's a mistake on the website. The issue is with dnf that it expects specfiles to end in ".spec", where as this is ".in". So it thinks it's a package name.
A way around it is:
sudo dnf install --setopt=strict=False `grep -E "^(Build)?Requires" 389-ds-base/rpm/389-ds-base.spec.in lib389/python-lib389.spec | grep -v -E '(name|MODULE)' | awk '{ print $2 }' | sed 's/%{python3_pkgversion}/3/g' | grep -v "^/" | grep -v pkgversion | sort | uniq | tr '\n' ' '`
This is a command that should be run on a single line,
Hope that helps,
Hi @William
I tried that command earlier and got errors of inspite of availability of the respective files.
"No package lib389/python-lib389.spec:"
&
"No package 389-ds-base/rpm/389-ds-base.spec.in"
I looked up regarding this for rpm build , and went through this http://directory.fedoraproject.org/docs/389ds/development/building.html#note... as to build spec files. But I am still facing issues , I am thinking of trying it on CentOS 7 @virtualbox . What's your say on it , my current os is Fedora 25.
Please suggest how to move from here.
Thanks.
On Tue, 2017-10-03 at 21:51 +0530, Dristi Butola wrote:
Hi @William
I tried that command earlier and got errors of inspite of availability of the respective files.
"No package lib389/python-lib389.spec:"
&
"No package 389-ds-base/rpm/389-ds-base.spec.in"
I looked up regarding this for rpm build , and went through this http://directory.fedoraproject.org/docs/389ds/development/building.html#note... as to build spec files. But I am still facing issues , I am thinking of trying it on CentOS 7 @virtualbox . What's your say on it , my current os is Fedora 25.
Please suggest how to move from here.
Centos7 might be a bit easier, Yum does not have the issues that DNF does. Give it a try and let me know how it goes,
I really want to improve this dependency creation process because at the moment it's not great :(
Hello William
I saw this project listing on outreachy project to be having good number of filled already. Just wanted to know if you have already got a strong candidate :) so that I can look for alternates.
Thanks
On Wed, Oct 4, 2017 at 4:57 AM, William Brown wibrown@redhat.com wrote:
On Tue, 2017-10-03 at 21:51 +0530, Dristi Butola wrote:
Hi @William
I tried that command earlier and got errors of inspite of availability
of
the respective files.
"No package lib389/python-lib389.spec:"
&
"No package 389-ds-base/rpm/389-ds-base.spec.in"
I looked up regarding this for rpm build , and went through this http://directory.fedoraproject.org/docs/389ds/development/building.html#
notes
as to build spec files. But I am still facing issues , I am thinking of trying it on CentOS 7 @virtualbox . What's your say on it , my current os is Fedora 25.
Please suggest how to move from here.
Centos7 might be a bit easier, Yum does not have the issues that DNF does. Give it a try and let me know how it goes,
I really want to improve this dependency creation process because at the moment it's not great :(
-- Sincerely,
William Brown Software Engineer Red Hat, Australia/Brisbane
389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
389-users@lists.fedoraproject.org
-
Dristi Butola -
William Brown