Hi Orion,
Thank you for helping us! Let me make sure I have the process correct:
1. Perform rpmbuild via the following command:
rpmbuild -ba SPECS/dmtcp.spec
2. Run the SRPM against the spec fedora-review as follows:
fedora-review --rpm-spec -n rpmbuild/SRPMS/dmtcp-2.6.1~rc1-0.1.fc30.src.rpm
3. Correct all the issues from the produced file /home/fedora/pgrosu/dmtcp/review.txt
4. Rerun Step 1, to generate the SRPM and provide that with the SPEC at a web-accessible location.
5. File a review of the package via Bugzilla at the following location:
https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review
6. Once approved create a unretiring ticket issue via:
https://pagure.io/releng/new_issue?template=package_unretirement&title=Unretire%20%3Cpkgname%3E
7. Not sure how to restore contents on GIT (though it says as necessary, but will ask you when I get there if it is okay).
Would the following be a good place or is there a better one for how to use fedora-review:
https://www.systutorials.com/docs/linux/man/1-fedora-review/
Thanks,
Paul
Thank you for helping us! Let me make sure I have the process correct:
1. Perform rpmbuild via the following command:
rpmbuild -ba SPECS/dmtcp.spec
2. Run the SRPM against the spec fedora-review as follows:
fedora-review --rpm-spec -n rpmbuild/SRPMS/dmtcp-2.6.1~rc1-0.1.fc30.src.rpm
3. Correct all the issues from the produced file /home/fedora/pgrosu/dmtcp/review.txt
4. Rerun Step 1, to generate the SRPM and provide that with the SPEC at a web-accessible location.
5. File a review of the package via Bugzilla at the following location:
https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora&format=fedora-review
6. Once approved create a unretiring ticket issue via:
https://pagure.io/releng/new_issue?template=package_unretirement&title=Unretire%20%3Cpkgname%3E
7. Not sure how to restore contents on GIT (though it says as necessary, but will ask you when I get there if it is okay).
Would the following be a good place or is there a better one for how to use fedora-review:
https://www.systutorials.com/docs/linux/man/1-fedora-review/
Let me know if I am missing anything.
Paul
On Mon, Dec 16, 2019 at 9:46 PM Orion Poplawski <orion@xxxxxxxx> wrote:
Paul -
See:
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package
because the package has been retired for longer than 8 weeks it needs to
go through a new review. I would run fedora-review on the package and
file a review request bug.
You will need to post the spec and src.rpm in a public location for the
review.
HTH,
Orion
On 12/15/19 10:08 PM, Paul Grosu wrote:
> Hello Orion and Kevin,
>
> We are almost ready to submit an updated DMTCP version. Would you
> prefer we put the srpm/spec at a public location for a review request,
> or just use fedpkg?
>
> Also after performing Koji and running rpmlint on the srpm and spec, is
> there anything else we would need to do to ensure everything is proper?
>
> Best regards,
> Paul
>
> On Mon, Nov 25, 2019 at 2:14 AM Paul Grosu <pgrosu@xxxxxxxxx
> <mailto:pgrosu@xxxxxxxxx>> wrote:
>
> Hello Orion and Kevin,
>
> Orion, many thanks for sponsoring us! This helps will help us
> tremendously. I have tested a few server and the connection works
> great. Gene and I are very grateful!
>
> Kevin, thank you greatly also for helping us with sponsorship for
> the additional group.
>
> Best regards,
> Paul
>
> On Sat, Nov 23, 2019 at 11:58 AM Orion Poplawski <orion@xxxxxxxx
> <mailto:orion@xxxxxxxx>> wrote:
>
> Paul -
>
> I've sponsored you - welcome aboard.
>
> - Orion
>
> On 11/22/19 3:46 PM, Paul Grosu wrote:
> > Hello Kevin,
> >
> > That would help us out greatly and I filed the following
> ticket at this
> > weblink with an additional request for x86_64 machine along
> with aarch64:
> >
> > https://pagure.io/fedora-infrastructure/issue/8406
> >
> > In request we are dropping support for armv7, as our
> application is
> > geared mainly for the HPC community. Please let us know what
> would be
> > the next steps for us to connect. Once we have fully tested,
> we would
> > be able to proceed with the review process in order to be
> properly
> > sponsored. Orion Poplawski at the following comment
> >
> (https://github.com/dmtcp/dmtcp/issues/698#issuecomment-530401895)
> > offered to sponsor us once we perform the review, which
> dependent on our
> > testing.
> >
> > Thank you,
> > Paul
> >
> > On Thu, Nov 21, 2019 at 5:42 PM Kevin Fenzi <kevin@xxxxxxxxx
> <mailto:kevin@xxxxxxxxx>
> > <mailto:kevin@xxxxxxxxx <mailto:kevin@xxxxxxxxx>>> wrote:
> >
> > On Wed, Nov 20, 2019 at 10:31:19AM +0300, Vascom wrote:
> > > pgrosu - is your FAS name?
> > > Are you in packager group?
> >
> > Right. Normally you would need to be in the packager
> group to have
> > access to these machines. However, if you are working on
> some upstream
> > open source application and need access we can do that.
> Just file a
> > ticket and let us know what you are looking for:
> >
> > https://pagure.io/fedora-infrastructure/issues
> >
> > kevin
> > --
> > >
> > > ср, 20 нояб. 2019 г. в 10:20, Paul Grosu
> <pgrosu@xxxxxxxxx <mailto:pgrosu@xxxxxxxxx>
> > <mailto:pgrosu@xxxxxxxxx <mailto:pgrosu@xxxxxxxxx>>>:
> > > >
> > > > Hi Vascom,
> > > >
> > > > Thank you for the quick reply. I already added the
> SSH public
> > key, but when I try to ssh with my private key and enter the
> > username pgrosu at the (login:) it says "No supported
> authentication
> > methods available". Does it mean I should wait a day for
> it to go
> > through, or should I contact the admin?
> > > >
> > > > Thanks,
> > > > Paul
> > > >
> > > > On Wed, Nov 20, 2019 at 2:04 AM Vascom
> <vascom2@xxxxxxxxx <mailto:vascom2@xxxxxxxxx>
> > <mailto:vascom2@xxxxxxxxx <mailto:vascom2@xxxxxxxxx>>> wrote:
> > > >>
> > > >> You need to add your public ssh key at FAS page
> > > >> https://admin.fedoraproject.org/accounts
> > > >> And login via ssh.
> > > >>
> > > >> Read all information on
> > > >>
> >
> https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
> > > >>
> > > >> ср, 20 нояб. 2019 г. в 09:54, Paul Grosu
> <pgrosu@xxxxxxxxx <mailto:pgrosu@xxxxxxxxx>
> > <mailto:pgrosu@xxxxxxxxx <mailto:pgrosu@xxxxxxxxx>>>:
> > > >> >
> > > >> > Hello Fedora Development Community,
> > > >> >
> > > >> > I work at Northeastern University as a researcher
> in the
> > Gene Cooperman Lab, and will be supporting the DMTCP package
> > (https://apps.fedoraproject.org/packages/dmtcp) and
> DMTCP-devel
> > (https://apps.fedoraproject.org/packages/dmtcp-devel).
> We are about
> > to release a new version of the package but don't have a
> aarch-64
> > machine, and was wondering how to go about having access
> to one of
> > the test machines listed on the following weblink:
> >
> https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
> > > >> >
> > > >> > Please let me know how to proceed regarding
> getting access
> > to a test machine.
> > > >> >
> > > >> > Thank you,
> > > >> > Paul
> > > >> > _______________________________________________
> > > >> > devel mailing list --
> devel@xxxxxxxxxxxxxxxxxxxxxxx <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>>
> > > >> > To unsubscribe send an email to
> > devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>>
> > > >> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > >> > List Guidelines:
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > >> > List Archives:
> >
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> > > >> _______________________________________________
> > > >> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>>
> > > >> To unsubscribe send an email to
> > devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>>
> > > >> Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > >> List Guidelines:
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > >> List Archives:
> >
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> > > >
> > > > _______________________________________________
> > > > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>>
> > > > To unsubscribe send an email to
> > devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>>
> > > > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > > List Guidelines:
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > > List Archives:
> >
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> > > _______________________________________________
> > > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>>
> > > To unsubscribe send an email to
> > devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>>
> > > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines:
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives:
> >
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> > _______________________________________________
> > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>>
> > To unsubscribe send an email to
> devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>
> > <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>>
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> >
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> >
> >
> > _______________________________________________
> > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel@xxxxxxxxxxxxxxxxxxxxxxx>
> > To unsubscribe send an email to
> devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> <mailto:devel-leave@xxxxxxxxxxxxxxxxxxxxxxx>
> > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> >
>
>
> --
> Orion Poplawski
> Manager of NWRA Technical Systems 720-772-5637
> NWRA, Boulder/CoRA Office FAX: 303-415-9702
> 3380 Mitchell Lane orion@xxxxxxxx <mailto:orion@xxxxxxxx>
> Boulder, CO 80301 https://www.nwra.com/
>
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@xxxxxxxx
Boulder, CO 80301 https://www.nwra.com/
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
