RE: Query on upgrading the Fedora package
Hi Christopher, Thanks for the detailed information. Regards, Muneendra. -Original Message- From: Christopher Engelhard [mailto:c...@lcts.de] Sent: Friday, August 28, 2020 2:26 PM To: devel@lists.fedoraproject.org Subject: Re: Query on upgrading the Fedora package Hi Muneendra, On 28.08.20 10:47, Muneendra Kumar M via devel wrote: > After stable time i.e 14 day's the updates will be automatically > moved to stable .Is this correct. That is the default yes, but you can configure it differently in the Bodhi web interface if you choose. Check out the EPEL Guidelines if you're unsure [1][2]. Personally, I disable all automatic pushing to stable for EPEL, because I try to align updates there with major updates to the underlying CentOS/RHEL release & give it enough time in Fedora to iron out any issues - the package will still be available in the testing repo for those who like to try it early. Best, Christopher [1] https://fedoraproject.org/wiki/EPEL_Updates_Policy [2] https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Query on upgrading the Fedora package
Hi Muneendra, On 28.08.20 10:47, Muneendra Kumar M via devel wrote: > After stable time i.e 14 day's the updates will be automatically moved to > stable .Is this correct. That is the default yes, but you can configure it differently in the Bodhi web interface if you choose. Check out the EPEL Guidelines if you're unsure [1][2]. Personally, I disable all automatic pushing to stable for EPEL, because I try to align updates there with major updates to the underlying CentOS/RHEL release & give it enough time in Fedora to iron out any issues - the package will still be available in the testing repo for those who like to try it early. Best, Christopher [1] https://fedoraproject.org/wiki/EPEL_Updates_Policy [2] https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
RE: Query on upgrading the Fedora package
Hi Chrstopher, Thanks for the info. I have run the below command for update Fedpkg update --type enhancement. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-77b06c3bc1 After stable time i.e 14 day's the updates will be automatically moved to stable .Is this correct. Regards, Muneendra. -Original Message- From: Christopher Engelhard [mailto:c...@lcts.de] Sent: Friday, August 28, 2020 1:45 PM To: Development discussions related to Fedora Subject: Re: Query on upgrading the Fedora package On 28.08.20 10:04, Muneendra Kumar M wrote: > Do I need to call fedpkg update --type enhancement after fedpkg build > for > epel8 ? Yes. Any branch that is Bodhi-enabled (normally any branch except rawhide & epel8-playground) will require a 'fedpkg update' to actually submit the build to the repositories. See here the documentation [1][2] for more info. Christopher [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#bodhi-enabling [2] https://fedoraproject.org/wiki/Package_maintenance_guide ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Query on upgrading the Fedora package
On 28.08.20 10:04, Muneendra Kumar M wrote: > Do I need to call fedpkg update --type enhancement after fedpkg build for > epel8 ? Yes. Any branch that is Bodhi-enabled (normally any branch except rawhide & epel8-playground) will require a 'fedpkg update' to actually submit the build to the repositories. See here the documentation [1][2] for more info. Christopher [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#bodhi-enabling [2] https://fedoraproject.org/wiki/Package_maintenance_guide ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
RE: Query on upgrading the Fedora package
Hi Christopher, A small doubt . Do I need to call fedpkg update --type enhancement after fedpkg build for epel8 ? Regards, Muneendra. -Original Message- From: Muneendra Kumar M [mailto:muneendra.ku...@broadcom.com] Sent: Friday, August 28, 2020 1:00 PM To: 'Development discussions related to Fedora' Cc: 'c...@lcts.de' ; 'Jonathan Wakely' ; 'Josef Ridky' Subject: RE: Query on upgrading the Fedora package Hi Christopher, I did the below steps to upgrade my package to EPEL8 and fedpkg build was success. https://koji.fedoraproject.org/koji/buildinfo?buildID=1602105 Do I need to do anything more for the same. As the below link still shows the older version. https://src.fedoraproject.org/rpms/fctxpd Release Stable versionFedora 34 fctxpd-0.2-1.20200827gitccbaf3a.fc34Fedora 31 fctxpd-0.1-1.20190813gitc195e67.fc31Fedora EPEL 8 fctxpd-0.1-1.20190813gitc195e67.el8 <== this is to be fctxpd-0.2-1.20200827gitccbaf3a.el8Steps: fedpkg clone fctxpd cd fctxpd/ git branch fedpkg switch-branch epel8 git branch git merge master fedpkg push fedpkg build Could you please help me on the same. Regards, Muneendra. -Original Message- From: Christopher Engelhard [mailto:c...@lcts.de] Sent: Thursday, August 27, 2020 6:04 PM To: devel@lists.fedoraproject.org Subject: Re: Query on upgrading the Fedora package On 27.08.20 13:27, Muneendra Kumar M via devel wrote: > Hi Josey, > Will the below steps work to upgrade the package for epel7. Epel works just like any other Fedora branch, so unless there are differences in dependencies on CentOS/RHEL vs Fedora (doesn't seem to be the case, as you already have the old EPEL builds) just merging master and building should work. If there are incompatibilities you can either adapt the spec after merging or deal with them with conditionals in the master spec file. Christopher ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
RE: Query on upgrading the Fedora package
Hi Christopher, I did the below steps to upgrade my package to EPEL8 and fedpkg build was success. https://koji.fedoraproject.org/koji/buildinfo?buildID=1602105 Do I need to do anything more for the same. As the below link still shows the older version. https://src.fedoraproject.org/rpms/fctxpd Release Stable versionFedora 34 fctxpd-0.2-1.20200827gitccbaf3a.fc34Fedora 31 fctxpd-0.1-1.20190813gitc195e67.fc31Fedora EPEL 8 fctxpd-0.1-1.20190813gitc195e67.el8 <== this is to be fctxpd-0.2-1.20200827gitccbaf3a.el8Steps: fedpkg clone fctxpd cd fctxpd/ git branch fedpkg switch-branch epel8 git branch git merge master fedpkg push fedpkg build Could you please help me on the same. Regards, Muneendra. -Original Message- From: Christopher Engelhard [mailto:c...@lcts.de] Sent: Thursday, August 27, 2020 6:04 PM To: devel@lists.fedoraproject.org Subject: Re: Query on upgrading the Fedora package On 27.08.20 13:27, Muneendra Kumar M via devel wrote: > Hi Josey, > Will the below steps work to upgrade the package for epel7. Epel works just like any other Fedora branch, so unless there are differences in dependencies on CentOS/RHEL vs Fedora (doesn't seem to be the case, as you already have the old EPEL builds) just merging master and building should work. If there are incompatibilities you can either adapt the spec after merging or deal with them with conditionals in the master spec file. Christopher ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Query on upgrading the Fedora package
On 27.08.20 13:27, Muneendra Kumar M via devel wrote: > Hi Josey, > Will the below steps work to upgrade the package for epel7. Epel works just like any other Fedora branch, so unless there are differences in dependencies on CentOS/RHEL vs Fedora (doesn't seem to be the case, as you already have the old EPEL builds) just merging master and building should work. If there are incompatibilities you can either adapt the spec after merging or deal with them with conditionals in the master spec file. Christopher ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Query on upgrading the Fedora package
In theory, it should be fine, but opinion from someone, who works with epel regularly would be better. Josef Ridky Software Engineer Core Services Team Red Hat Czech, s.r.o. - Original Message - | From: "Muneendra Kumar M via devel" | To: "Josef Ridky" | Cc: "Development discussions related to Fedora" , "Jonathan Wakely" | , "Muneendra Kumar M" | Sent: Thursday, August 27, 2020 1:27:59 PM | Subject: RE: Query on upgrading the Fedora package | | Hi Josey, | Will the below steps work to upgrade the package for epel7. | Please let me know if there is any issue. | fedpkg clone fctxpd | cd fctxpd/ | git branch | fedpkg switch-branch epel7 | git branch | git merge master | fedpkg push | fedpkg build | | Regards, | Muneendra. | -Original Message- | From: Muneendra Kumar M [mailto:muneendra.ku...@broadcom.com] | Sent: Thursday, August 27, 2020 4:42 PM | To: 'Josef Ridky' | Cc: 'Development discussions related to Fedora' | ; 'Jonathan Wakely' | | Subject: RE: Query on upgrading the Fedora package | | Hi Josey, | Thanks for sharing the info and I was able to fix the issue and upgrade the | package to FC34. | | How do I upgrade my package to EPEL 7 and EPEL 8 which still has old version | of package(fctxpd-0.1-1.20190813gitc195e67.el8). | Any help here will be great. | | | Release Stable versionFedora | 34fctxpd-0.2-1.20200827gitccbaf3a.fc34Fedora EPEL | 8 fctxpd-0.1-1.20190813gitc195e67.el8 | Fedora EPEL 7 fctxpd-0.1-1.20190813gitc195e67.el7 | | Regards, | Muneendra. | | -Original Message- | From: Josef Ridky [mailto:jri...@redhat.com] | Sent: Thursday, August 27, 2020 4:24 PM | To: Muneendra Kumar M | Cc: Development discussions related to Fedora | ; Jonathan Wakely | Subject: Re: Query on upgrading the Fedora package | | fedpkg provided you task URL, where you can find all logs related to current | build. | In your case, taks URL is | https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 | | Under this URL, you find links to sub-builds of your package (sub-build mean | your package built for specific architecture - x86_64, arm, ppc64le etc). | Each sub-build contains it's own list of logs. Most important one for you | are root.log (where issues with dependencies for your package during dnf | install query are mentioned) and build.log where you can find full log from | package build. In this build log is available the line I've mentioned in my | previous message. | | When you run tar -xzf fctxpd-ccbaf3a.tar.gz, what is the name of folder, | where you will find unpacked files from that tarball? | Use such name as param for %setup/%autosetup directive in your spec file | | e.g. %setup -n name_of_my_folder | | Regards | | Josef Ridky | Software Engineer | Core Services Team | Red Hat Czech, s.r.o. | | - Original Message - | | From: "Muneendra Kumar M" | | To: "Josef Ridky" , "Development discussions | | related to Fedora" | | Cc: "Jonathan Wakely" | | Sent: Thursday, August 27, 2020 12:19:37 PM | | Subject: RE: Query on upgrading the Fedora package | | | | Hi Josey, | | But the src.rpm has a fctxpd-ccbaf3a.tar.gz and fctxpd.spec. | | And when we extract fctxpd-ccbaf3a.tar.gz it has | | bsn-fc-txpd-ccbaf3a0cbadaaef727bcb53c1ac543fa049. | | Can you please let me know whether iam missing something. | | | | And how did u see the below error. | | | | /var/tmp/rpm-tmp.0K14Wz: line 39: cd: | | bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or | | director | | | | Regards, | | Muneendra. | | | | | | -Original Message- | | From: Josef Ridky [mailto:jri...@redhat.com] | | Sent: Thursday, August 27, 2020 3:37 PM | | To: Development discussions related to Fedora | | | | Cc: Jonathan Wakely ; Muneendra Kumar M | | | | Subject: Re: Query on upgrading the Fedora package | | | | Take a look at build.log that is available at provided koji URL. | | | | /var/tmp/rpm-tmp.0K14Wz: line 39: cd: | | bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or | | directory | | | | That's the reason of your build failure. | | | | Josef Ridky | | Software Engineer | | Core Services Team | | Red Hat Czech, s.r.o. | | | | - Original Message - | | | From: "Muneendra Kumar M via devel" | | | To: "Jonathan Wakely" , "Development | | discussions related to Fedora" | | | | | | Cc: "Muneendra Kumar M" | | | Sent: Thursday, August 27, 2020 11:58:22 AM | | | Subject: RE: Query on upgrading the Fedora package | | | | | | Hi Jonathan, | | | As per the below guidelines I tried the below steps but iam getting | | | the below error when I run fedpkg scratch-build --srpm. | | | | | | And how can I see the error logs? | | | Could you please let me know what went wrong. | | | | | | fedpkg clone fctxpd | | | cd fctxpd | | | edited the spec file | | | fedpkg srpm | | | | | | fed
RE: Query on upgrading the Fedora package
Hi Josey, Will the below steps work to upgrade the package for epel7. Please let me know if there is any issue. fedpkg clone fctxpd cd fctxpd/ git branch fedpkg switch-branch epel7 git branch git merge master fedpkg push fedpkg build Regards, Muneendra. -Original Message- From: Muneendra Kumar M [mailto:muneendra.ku...@broadcom.com] Sent: Thursday, August 27, 2020 4:42 PM To: 'Josef Ridky' Cc: 'Development discussions related to Fedora' ; 'Jonathan Wakely' Subject: RE: Query on upgrading the Fedora package Hi Josey, Thanks for sharing the info and I was able to fix the issue and upgrade the package to FC34. How do I upgrade my package to EPEL 7 and EPEL 8 which still has old version of package(fctxpd-0.1-1.20190813gitc195e67.el8). Any help here will be great. Release Stable versionFedora 34 fctxpd-0.2-1.20200827gitccbaf3a.fc34Fedora EPEL 8 fctxpd-0.1-1.20190813gitc195e67.el8 Fedora EPEL 7 fctxpd-0.1-1.20190813gitc195e67.el7 Regards, Muneendra. -Original Message- From: Josef Ridky [mailto:jri...@redhat.com] Sent: Thursday, August 27, 2020 4:24 PM To: Muneendra Kumar M Cc: Development discussions related to Fedora ; Jonathan Wakely Subject: Re: Query on upgrading the Fedora package fedpkg provided you task URL, where you can find all logs related to current build. In your case, taks URL is https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 Under this URL, you find links to sub-builds of your package (sub-build mean your package built for specific architecture - x86_64, arm, ppc64le etc). Each sub-build contains it's own list of logs. Most important one for you are root.log (where issues with dependencies for your package during dnf install query are mentioned) and build.log where you can find full log from package build. In this build log is available the line I've mentioned in my previous message. When you run tar -xzf fctxpd-ccbaf3a.tar.gz, what is the name of folder, where you will find unpacked files from that tarball? Use such name as param for %setup/%autosetup directive in your spec file e.g. %setup -n name_of_my_folder Regards Josef Ridky Software Engineer Core Services Team Red Hat Czech, s.r.o. - Original Message - | From: "Muneendra Kumar M" | To: "Josef Ridky" , "Development discussions | related to Fedora" | Cc: "Jonathan Wakely" | Sent: Thursday, August 27, 2020 12:19:37 PM | Subject: RE: Query on upgrading the Fedora package | | Hi Josey, | But the src.rpm has a fctxpd-ccbaf3a.tar.gz and fctxpd.spec. | And when we extract fctxpd-ccbaf3a.tar.gz it has | bsn-fc-txpd-ccbaf3a0cbadaaef727bcb53c1ac543fa049. | Can you please let me know whether iam missing something. | | And how did u see the below error. | | /var/tmp/rpm-tmp.0K14Wz: line 39: cd: | bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or | director | | Regards, | Muneendra. | | | -Original Message- | From: Josef Ridky [mailto:jri...@redhat.com] | Sent: Thursday, August 27, 2020 3:37 PM | To: Development discussions related to Fedora | | Cc: Jonathan Wakely ; Muneendra Kumar M | | Subject: Re: Query on upgrading the Fedora package | | Take a look at build.log that is available at provided koji URL. | | /var/tmp/rpm-tmp.0K14Wz: line 39: cd: | bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or | directory | | That's the reason of your build failure. | | Josef Ridky | Software Engineer | Core Services Team | Red Hat Czech, s.r.o. | | - Original Message - | | From: "Muneendra Kumar M via devel" | | To: "Jonathan Wakely" , "Development | discussions related to Fedora" | | | | Cc: "Muneendra Kumar M" | | Sent: Thursday, August 27, 2020 11:58:22 AM | | Subject: RE: Query on upgrading the Fedora package | | | | Hi Jonathan, | | As per the below guidelines I tried the below steps but iam getting | | the below error when I run fedpkg scratch-build --srpm. | | | | And how can I see the error logs? | | Could you please let me know what went wrong. | | | | fedpkg clone fctxpd | | cd fctxpd | | edited the spec file | | fedpkg srpm | | | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm And I got the | | error as below | | | | | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm | | /usr/lib/python3.7/site-packages/koji/util.py:53: DeprecationWarning: | | Please use gssapi_login instead, krb_login will be removed in koji 1.22 | | warnings.warn(message, DeprecationWarning) | | [] 100% 00:00:02 336.90 KiB | | 141.66 KiB/sec Building fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm | | for rawhide Created task: 50235166 Task info: | | https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 | | Watching tasks (this may be safely interrupted)... | | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | | free | | 50235166 build (rawhide, fctxpd-0.2-1.20200827g
RE: Query on upgrading the Fedora package
Hi Josey, Thanks for sharing the info and I was able to fix the issue and upgrade the package to FC34. How do I upgrade my package to EPEL 7 and EPEL 8 which still has old version of package(fctxpd-0.1-1.20190813gitc195e67.el8). Any help here will be great. Release Stable versionFedora 34 fctxpd-0.2-1.20200827gitccbaf3a.fc34Fedora EPEL 8 fctxpd-0.1-1.20190813gitc195e67.el8 Fedora EPEL 7 fctxpd-0.1-1.20190813gitc195e67.el7 Regards, Muneendra. -Original Message- From: Josef Ridky [mailto:jri...@redhat.com] Sent: Thursday, August 27, 2020 4:24 PM To: Muneendra Kumar M Cc: Development discussions related to Fedora ; Jonathan Wakely Subject: Re: Query on upgrading the Fedora package fedpkg provided you task URL, where you can find all logs related to current build. In your case, taks URL is https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 Under this URL, you find links to sub-builds of your package (sub-build mean your package built for specific architecture - x86_64, arm, ppc64le etc). Each sub-build contains it's own list of logs. Most important one for you are root.log (where issues with dependencies for your package during dnf install query are mentioned) and build.log where you can find full log from package build. In this build log is available the line I've mentioned in my previous message. When you run tar -xzf fctxpd-ccbaf3a.tar.gz, what is the name of folder, where you will find unpacked files from that tarball? Use such name as param for %setup/%autosetup directive in your spec file e.g. %setup -n name_of_my_folder Regards Josef Ridky Software Engineer Core Services Team Red Hat Czech, s.r.o. - Original Message - | From: "Muneendra Kumar M" | To: "Josef Ridky" , "Development discussions | related to Fedora" | Cc: "Jonathan Wakely" | Sent: Thursday, August 27, 2020 12:19:37 PM | Subject: RE: Query on upgrading the Fedora package | | Hi Josey, | But the src.rpm has a fctxpd-ccbaf3a.tar.gz and fctxpd.spec. | And when we extract fctxpd-ccbaf3a.tar.gz it has | bsn-fc-txpd-ccbaf3a0cbadaaef727bcb53c1ac543fa049. | Can you please let me know whether iam missing something. | | And how did u see the below error. | | /var/tmp/rpm-tmp.0K14Wz: line 39: cd: | bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or | director | | Regards, | Muneendra. | | | -Original Message- | From: Josef Ridky [mailto:jri...@redhat.com] | Sent: Thursday, August 27, 2020 3:37 PM | To: Development discussions related to Fedora | | Cc: Jonathan Wakely ; Muneendra Kumar M | | Subject: Re: Query on upgrading the Fedora package | | Take a look at build.log that is available at provided koji URL. | | /var/tmp/rpm-tmp.0K14Wz: line 39: cd: | bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or | directory | | That's the reason of your build failure. | | Josef Ridky | Software Engineer | Core Services Team | Red Hat Czech, s.r.o. | | - Original Message - | | From: "Muneendra Kumar M via devel" | | To: "Jonathan Wakely" , "Development | discussions related to Fedora" | | | | Cc: "Muneendra Kumar M" | | Sent: Thursday, August 27, 2020 11:58:22 AM | | Subject: RE: Query on upgrading the Fedora package | | | | Hi Jonathan, | | As per the below guidelines I tried the below steps but iam getting | | the below error when I run fedpkg scratch-build --srpm. | | | | And how can I see the error logs? | | Could you please let me know what went wrong. | | | | fedpkg clone fctxpd | | cd fctxpd | | edited the spec file | | fedpkg srpm | | | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm And I got the | | error as below | | | | | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm | | /usr/lib/python3.7/site-packages/koji/util.py:53: DeprecationWarning: | | Please use gssapi_login instead, krb_login will be removed in koji 1.22 | | warnings.warn(message, DeprecationWarning) | | [] 100% 00:00:02 336.90 KiB | | 141.66 KiB/sec Building fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm | | for rawhide Created task: 50235166 Task info: | | https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 | | Watching tasks (this may be safely interrupted)... | | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | | free | | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | | free -> open (buildvm-x86-06.iad2.fedoraproject.org) | | 50235170 rebuildSRPM (noarch): closed | | 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): | | free | | 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | | x86_64): free | | 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | | ppc64le): free | | 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | | s390x): open (buildvm-s390x-23.s390.fedoraproject.org)
Re: Query on upgrading the Fedora package
fedpkg provided you task URL, where you can find all logs related to current build. In your case, taks URL is https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 Under this URL, you find links to sub-builds of your package (sub-build mean your package built for specific architecture - x86_64, arm, ppc64le etc). Each sub-build contains it's own list of logs. Most important one for you are root.log (where issues with dependencies for your package during dnf install query are mentioned) and build.log where you can find full log from package build. In this build log is available the line I've mentioned in my previous message. When you run tar -xzf fctxpd-ccbaf3a.tar.gz, what is the name of folder, where you will find unpacked files from that tarball? Use such name as param for %setup/%autosetup directive in your spec file e.g. %setup -n name_of_my_folder Regards Josef Ridky Software Engineer Core Services Team Red Hat Czech, s.r.o. - Original Message - | From: "Muneendra Kumar M" | To: "Josef Ridky" , "Development discussions related to Fedora" | Cc: "Jonathan Wakely" | Sent: Thursday, August 27, 2020 12:19:37 PM | Subject: RE: Query on upgrading the Fedora package | | Hi Josey, | But the src.rpm has a fctxpd-ccbaf3a.tar.gz and fctxpd.spec. | And when we extract fctxpd-ccbaf3a.tar.gz it has | bsn-fc-txpd-ccbaf3a0cbadaaef727bcb53c1ac543fa049. | Can you please let me know whether iam missing something. | | And how did u see the below error. | | /var/tmp/rpm-tmp.0K14Wz: line 39: cd: | bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or | director | | Regards, | Muneendra. | | | -Original Message- | From: Josef Ridky [mailto:jri...@redhat.com] | Sent: Thursday, August 27, 2020 3:37 PM | To: Development discussions related to Fedora | | Cc: Jonathan Wakely ; Muneendra Kumar M | | Subject: Re: Query on upgrading the Fedora package | | Take a look at build.log that is available at provided koji URL. | | /var/tmp/rpm-tmp.0K14Wz: line 39: cd: | bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or | directory | | That's the reason of your build failure. | | Josef Ridky | Software Engineer | Core Services Team | Red Hat Czech, s.r.o. | | - Original Message - | | From: "Muneendra Kumar M via devel" | | To: "Jonathan Wakely" , "Development | discussions related to Fedora" | | | | Cc: "Muneendra Kumar M" | | Sent: Thursday, August 27, 2020 11:58:22 AM | | Subject: RE: Query on upgrading the Fedora package | | | | Hi Jonathan, | | As per the below guidelines I tried the below steps but iam getting | | the below error when I run fedpkg scratch-build --srpm. | | | | And how can I see the error logs? | | Could you please let me know what went wrong. | | | | fedpkg clone fctxpd | | cd fctxpd | | edited the spec file | | fedpkg srpm | | | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm And I got the | | error as below | | | | | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm | | /usr/lib/python3.7/site-packages/koji/util.py:53: DeprecationWarning: | | Please use gssapi_login instead, krb_login will be removed in koji 1.22 | | warnings.warn(message, DeprecationWarning) | | [] 100% 00:00:02 336.90 KiB 141.66 | | KiB/sec Building fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm for | | rawhide Created task: 50235166 Task info: | | https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 | | Watching tasks (this may be safely interrupted)... | | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | | free | | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | | free -> open (buildvm-x86-06.iad2.fedoraproject.org) | | 50235170 rebuildSRPM (noarch): closed | | 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): | | free | | 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | | x86_64): free | | 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | | ppc64le): free | | 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | | s390x): open (buildvm-s390x-23.s390.fedoraproject.org) | | 50235374 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | | aarch64): open (buildvm-a64-04.iad2.fedoraproject.org) | | 50235371 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | | armv7hl): open (buildvm-a32-05.iad2.fedoraproject.org) | | 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): | | free -> FAILED: BuildError: error building package (arch i686), mock | | exited with status 1; see build.log or root.log for more information | | 2 free 4 open 1 done 1 failed | | 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | | x86_64): free -> FAILED: BuildError: error building package (arch | | x86_64), mock exited with status 1
RE: Query on upgrading the Fedora package
Hi Josey, Thanks for pointing out the issue. I fixed the issue and it build successfully. Thanks for your quick help. Regards, Muneendra. -Original Message- From: Muneendra Kumar M [mailto:muneendra.ku...@broadcom.com] Sent: Thursday, August 27, 2020 3:50 PM To: 'Josef Ridky' ; 'Development discussions related to Fedora' Cc: 'Jonathan Wakely' Subject: RE: Query on upgrading the Fedora package Hi Josey, But the src.rpm has a fctxpd-ccbaf3a.tar.gz and fctxpd.spec. And when we extract fctxpd-ccbaf3a.tar.gz it has bsn-fc-txpd-ccbaf3a0cbadaaef727bcb53c1ac543fa049. Can you please let me know whether iam missing something. And how did u see the below error. /var/tmp/rpm-tmp.0K14Wz: line 39: cd: bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or director Regards, Muneendra. -Original Message- From: Josef Ridky [mailto:jri...@redhat.com] Sent: Thursday, August 27, 2020 3:37 PM To: Development discussions related to Fedora Cc: Jonathan Wakely ; Muneendra Kumar M Subject: Re: Query on upgrading the Fedora package Take a look at build.log that is available at provided koji URL. /var/tmp/rpm-tmp.0K14Wz: line 39: cd: bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or directory That's the reason of your build failure. Josef Ridky Software Engineer Core Services Team Red Hat Czech, s.r.o. - Original Message - | From: "Muneendra Kumar M via devel" | To: "Jonathan Wakely" , "Development discussions related to Fedora" | | Cc: "Muneendra Kumar M" | Sent: Thursday, August 27, 2020 11:58:22 AM | Subject: RE: Query on upgrading the Fedora package | | Hi Jonathan, | As per the below guidelines I tried the below steps but iam getting | the below error when I run fedpkg scratch-build --srpm. | | And how can I see the error logs? | Could you please let me know what went wrong. | | fedpkg clone fctxpd | cd fctxpd | edited the spec file | fedpkg srpm | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm And I got the | error as below | | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm | /usr/lib/python3.7/site-packages/koji/util.py:53: DeprecationWarning: | Please use gssapi_login instead, krb_login will be removed in koji 1.22 | warnings.warn(message, DeprecationWarning) | [] 100% 00:00:02 336.90 KiB 141.66 | KiB/sec Building fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm for | rawhide Created task: 50235166 Task info: | https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 | Watching tasks (this may be safely interrupted)... | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | free | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | free -> open (buildvm-x86-06.iad2.fedoraproject.org) | 50235170 rebuildSRPM (noarch): closed | 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): | free | 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | x86_64): free | 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | ppc64le): free | 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | s390x): open (buildvm-s390x-23.s390.fedoraproject.org) | 50235374 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | aarch64): open (buildvm-a64-04.iad2.fedoraproject.org) | 50235371 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | armv7hl): open (buildvm-a32-05.iad2.fedoraproject.org) | 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): | free -> FAILED: BuildError: error building package (arch i686), mock | exited with status 1; see build.log or root.log for more information | 2 free 4 open 1 done 1 failed | 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | x86_64): free -> FAILED: BuildError: error building package (arch | x86_64), mock exited with status 1; see build.log or root.log for more information | 1 free 4 open 1 done 2 failed | 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | ppc64le): free -> open (buildvm-ppc64le-25.iad2.fedoraproject.org) | 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | s390x): open (buildvm-s390x-23.s390.fedoraproject.org) -> FAILED: | BuildError: error building package (arch s390x), mock exited with | status 1; see build.log or root.log for more information | 0 free 4 open 1 done 3 failed | 50235374 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | aarch64): open (buildvm-a64-04.iad2.fedoraproject.org) -> FAILED: | BuildError: error building package (arch aarch64), mock exited with | status 1; see build.log or root.log for more information | 0 free 3 open 1 done 4 failed | 50235371 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | armv7hl): open (buildvm-a32-05.iad2.fedoraproject.org) -> FAILED: | BuildError: error building package (arch armv7hl), mo
RE: Query on upgrading the Fedora package
Hi Josey, But the src.rpm has a fctxpd-ccbaf3a.tar.gz and fctxpd.spec. And when we extract fctxpd-ccbaf3a.tar.gz it has bsn-fc-txpd-ccbaf3a0cbadaaef727bcb53c1ac543fa049. Can you please let me know whether iam missing something. And how did u see the below error. /var/tmp/rpm-tmp.0K14Wz: line 39: cd: bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or director Regards, Muneendra. -Original Message- From: Josef Ridky [mailto:jri...@redhat.com] Sent: Thursday, August 27, 2020 3:37 PM To: Development discussions related to Fedora Cc: Jonathan Wakely ; Muneendra Kumar M Subject: Re: Query on upgrading the Fedora package Take a look at build.log that is available at provided koji URL. /var/tmp/rpm-tmp.0K14Wz: line 39: cd: bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or directory That's the reason of your build failure. Josef Ridky Software Engineer Core Services Team Red Hat Czech, s.r.o. - Original Message - | From: "Muneendra Kumar M via devel" | To: "Jonathan Wakely" , "Development discussions related to Fedora" | | Cc: "Muneendra Kumar M" | Sent: Thursday, August 27, 2020 11:58:22 AM | Subject: RE: Query on upgrading the Fedora package | | Hi Jonathan, | As per the below guidelines I tried the below steps but iam getting | the below error when I run fedpkg scratch-build --srpm. | | And how can I see the error logs? | Could you please let me know what went wrong. | | fedpkg clone fctxpd | cd fctxpd | edited the spec file | fedpkg srpm | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm And I got the | error as below | | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm | /usr/lib/python3.7/site-packages/koji/util.py:53: DeprecationWarning: | Please use gssapi_login instead, krb_login will be removed in koji 1.22 | warnings.warn(message, DeprecationWarning) | [] 100% 00:00:02 336.90 KiB 141.66 | KiB/sec Building fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm for | rawhide Created task: 50235166 Task info: | https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 | Watching tasks (this may be safely interrupted)... | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | free | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | free -> open (buildvm-x86-06.iad2.fedoraproject.org) | 50235170 rebuildSRPM (noarch): closed | 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): | free | 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | x86_64): free | 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | ppc64le): free | 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | s390x): open (buildvm-s390x-23.s390.fedoraproject.org) | 50235374 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | aarch64): open (buildvm-a64-04.iad2.fedoraproject.org) | 50235371 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | armv7hl): open (buildvm-a32-05.iad2.fedoraproject.org) | 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): | free -> FAILED: BuildError: error building package (arch i686), mock | exited with status 1; see build.log or root.log for more information | 2 free 4 open 1 done 1 failed | 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | x86_64): free -> FAILED: BuildError: error building package (arch | x86_64), mock exited with status 1; see build.log or root.log for more information | 1 free 4 open 1 done 2 failed | 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | ppc64le): free -> open (buildvm-ppc64le-25.iad2.fedoraproject.org) | 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | s390x): open (buildvm-s390x-23.s390.fedoraproject.org) -> FAILED: | BuildError: error building package (arch s390x), mock exited with | status 1; see build.log or root.log for more information | 0 free 4 open 1 done 3 failed | 50235374 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | aarch64): open (buildvm-a64-04.iad2.fedoraproject.org) -> FAILED: | BuildError: error building package (arch aarch64), mock exited with | status 1; see build.log or root.log for more information | 0 free 3 open 1 done 4 failed | 50235371 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | armv7hl): open (buildvm-a32-05.iad2.fedoraproject.org) -> FAILED: | BuildError: error building package (arch armv7hl), mock exited with | status 1; see build.log or root.log for more information | 0 free 2 open 1 done 5 failed | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | open (buildvm-x86-06.iad2.fedoraproject.org) -> FAILED: BuildError: | error building package (arch armv7hl), mock exited with status 1; see | build.log or root.log for more information | 0 free 1 open 1 done 6 fai
Re: Query on upgrading the Fedora package
Take a look at build.log that is available at provided koji URL. /var/tmp/rpm-tmp.0K14Wz: line 39: cd: bsn-fc-txptd-ccbaf3a0cbadaaef727bcb53c1ac543fa049: No such file or directory That's the reason of your build failure. Josef Ridky Software Engineer Core Services Team Red Hat Czech, s.r.o. - Original Message - | From: "Muneendra Kumar M via devel" | To: "Jonathan Wakely" , "Development discussions related to Fedora" | | Cc: "Muneendra Kumar M" | Sent: Thursday, August 27, 2020 11:58:22 AM | Subject: RE: Query on upgrading the Fedora package | | Hi Jonathan, | As per the below guidelines I tried the below steps but iam getting the | below error when I run fedpkg scratch-build --srpm. | | And how can I see the error logs? | Could you please let me know what went wrong. | | fedpkg clone fctxpd | cd fctxpd | edited the spec file | fedpkg srpm | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm | And I got the error as below | | | fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm | /usr/lib/python3.7/site-packages/koji/util.py:53: DeprecationWarning: | Please use gssapi_login instead, krb_login will be removed in koji 1.22 | warnings.warn(message, DeprecationWarning) | [] 100% 00:00:02 336.90 KiB 141.66 | KiB/sec | Building fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm for rawhide | Created task: 50235166 | Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 | Watching tasks (this may be safely interrupted)... | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | free | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | free -> open (buildvm-x86-06.iad2.fedoraproject.org) | 50235170 rebuildSRPM (noarch): closed | 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): | free | 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | x86_64): free | 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | ppc64le): free | 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | s390x): open (buildvm-s390x-23.s390.fedoraproject.org) | 50235374 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | aarch64): open (buildvm-a64-04.iad2.fedoraproject.org) | 50235371 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | armv7hl): open (buildvm-a32-05.iad2.fedoraproject.org) | 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): | free -> FAILED: BuildError: error building package (arch i686), mock | exited with status 1; see build.log or root.log for more information | 2 free 4 open 1 done 1 failed | 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | x86_64): free -> FAILED: BuildError: error building package (arch x86_64), | mock exited with status 1; see build.log or root.log for more information | 1 free 4 open 1 done 2 failed | 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | ppc64le): free -> open (buildvm-ppc64le-25.iad2.fedoraproject.org) | 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | s390x): open (buildvm-s390x-23.s390.fedoraproject.org) -> FAILED: | BuildError: error building package (arch s390x), mock exited with status | 1; see build.log or root.log for more information | 0 free 4 open 1 done 3 failed | 50235374 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | aarch64): open (buildvm-a64-04.iad2.fedoraproject.org) -> FAILED: | BuildError: error building package (arch aarch64), mock exited with status | 1; see build.log or root.log for more information | 0 free 3 open 1 done 4 failed | 50235371 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | armv7hl): open (buildvm-a32-05.iad2.fedoraproject.org) -> FAILED: | BuildError: error building package (arch armv7hl), mock exited with status | 1; see build.log or root.log for more information | 0 free 2 open 1 done 5 failed | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): | open (buildvm-x86-06.iad2.fedoraproject.org) -> FAILED: BuildError: error | building package (arch armv7hl), mock exited with status 1; see build.log | or root.log for more information | 0 free 1 open 1 done 6 failed | 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, | ppc64le): open (buildvm-ppc64le-25.iad2.fedoraproject.org) -> FAILED: | BuildError: error building package (arch ppc64le), mock exited with status | 1; see build.log or root.log for more information | 0 free 0 open 1 done 7 failed | | 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm) | failed | a | | Regards, | Muneendra. | | | -Original Message- | From: Jonathan Wakely [mailto:jwak...@fedoraproject.org] | Sent: Wednesday, July 29, 2020 5:16 PM | To: Development discussions related to Fedora | | Cc: Muneendra Kumar M | Subject: Re:
RE: Query on upgrading the Fedora package
Hi Jonathan, As per the below guidelines I tried the below steps but iam getting the below error when I run fedpkg scratch-build --srpm. And how can I see the error logs? Could you please let me know what went wrong. fedpkg clone fctxpd cd fctxpd edited the spec file fedpkg srpm fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm And I got the error as below fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm /usr/lib/python3.7/site-packages/koji/util.py:53: DeprecationWarning: Please use gssapi_login instead, krb_login will be removed in koji 1.22 warnings.warn(message, DeprecationWarning) [] 100% 00:00:02 336.90 KiB 141.66 KiB/sec Building fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm for rawhide Created task: 50235166 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=50235166 Watching tasks (this may be safely interrupted)... 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): free 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): free -> open (buildvm-x86-06.iad2.fedoraproject.org) 50235170 rebuildSRPM (noarch): closed 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): free 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, x86_64): free 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, ppc64le): free 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, s390x): open (buildvm-s390x-23.s390.fedoraproject.org) 50235374 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, aarch64): open (buildvm-a64-04.iad2.fedoraproject.org) 50235371 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, armv7hl): open (buildvm-a32-05.iad2.fedoraproject.org) 50235372 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, i686): free -> FAILED: BuildError: error building package (arch i686), mock exited with status 1; see build.log or root.log for more information 2 free 4 open 1 done 1 failed 50235373 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, x86_64): free -> FAILED: BuildError: error building package (arch x86_64), mock exited with status 1; see build.log or root.log for more information 1 free 4 open 1 done 2 failed 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, ppc64le): free -> open (buildvm-ppc64le-25.iad2.fedoraproject.org) 50235376 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, s390x): open (buildvm-s390x-23.s390.fedoraproject.org) -> FAILED: BuildError: error building package (arch s390x), mock exited with status 1; see build.log or root.log for more information 0 free 4 open 1 done 3 failed 50235374 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, aarch64): open (buildvm-a64-04.iad2.fedoraproject.org) -> FAILED: BuildError: error building package (arch aarch64), mock exited with status 1; see build.log or root.log for more information 0 free 3 open 1 done 4 failed 50235371 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, armv7hl): open (buildvm-a32-05.iad2.fedoraproject.org) -> FAILED: BuildError: error building package (arch armv7hl), mock exited with status 1; see build.log or root.log for more information 0 free 2 open 1 done 5 failed 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm): open (buildvm-x86-06.iad2.fedoraproject.org) -> FAILED: BuildError: error building package (arch armv7hl), mock exited with status 1; see build.log or root.log for more information 0 free 1 open 1 done 6 failed 50235375 buildArch (fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm, ppc64le): open (buildvm-ppc64le-25.iad2.fedoraproject.org) -> FAILED: BuildError: error building package (arch ppc64le), mock exited with status 1; see build.log or root.log for more information 0 free 0 open 1 done 7 failed 50235166 build (rawhide, fctxpd-0.2-1.20200827gitccbaf3a.fc34.src.rpm) failed a Regards, Muneendra. -Original Message- From: Jonathan Wakely [mailto:jwak...@fedoraproject.org] Sent: Wednesday, July 29, 2020 5:16 PM To: Development discussions related to Fedora Cc: Muneendra Kumar M Subject: Re: Query on upgrading the Fedora package >I don't know what part of the procedure you're unclear about, so here's >a summary of the entire process from start to finish. > >Get the package sources: > >fedpkg clone fctxpd >cd fctxpd > >Now download the new upstream code. >Optionally verify the package was downloaded correctly by checking a >SHA or other hash. > >Open the fctxpd.spec file in your preferred editor. Update the various >versions (commit, snapshotdate etc.) and add a new entry to the >%changelog section. Save the file. > >Create a SRPM from the changed (but not committed spec file): Oops, this was meant to say: Create a SRPM from the changed (but not committed) spec file: >fedpkg srpm > >Run a scratch build in
RE: Query on upgrading the Fedora package
Hi Jonathan, Thanks for the info. Regards, Muneendra. -Original Message- From: Jonathan Wakely [mailto:jwak...@fedoraproject.org] Sent: Wednesday, July 29, 2020 5:16 PM To: Development discussions related to Fedora Cc: Muneendra Kumar M Subject: Re: Query on upgrading the Fedora package >I don't know what part of the procedure you're unclear about, so here's >a summary of the entire process from start to finish. > >Get the package sources: > >fedpkg clone fctxpd >cd fctxpd > >Now download the new upstream code. >Optionally verify the package was downloaded correctly by checking a >SHA or other hash. > >Open the fctxpd.spec file in your preferred editor. Update the various >versions (commit, snapshotdate etc.) and add a new entry to the >%changelog section. Save the file. > >Create a SRPM from the changed (but not committed spec file): Oops, this was meant to say: Create a SRPM from the changed (but not committed) spec file: >fedpkg srpm > >Run a scratch build in the koji build system: > >fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm > >Wait for the results, check them, fix any problems. > >Once you have a working package, commit your changes to the spec file: > >fedpkg new-sources NEW-UPSTREAM-TARBALL.tar.gz fedpkg commit -c And your mail software seems to have lost a newline between these two commands: fedpkg new-sources NEW-UPSTREAM-TARBALL.tar.gz fedpkg commit -c > >And publish them: > >fedpkg push > >And do the real build: > >fedpkg build I should also say that these steps are not the _only_ way to do it (they're not even the way I would do it most of the time). But they should be a simple-to-follow sequence that is relatively hard to screw up. Use 'man fedpkg' to find out more about each step, and see these links for additonal background information: https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/ https://fedoraproject.org/wiki/Package_maintenance_guide https://fedoraproject.org/wiki/Package_update_HOWTO ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Query on upgrading the Fedora package
I don't know what part of the procedure you're unclear about, so here's a summary of the entire process from start to finish. Get the package sources: fedpkg clone fctxpd cd fctxpd Now download the new upstream code. Optionally verify the package was downloaded correctly by checking a SHA or other hash. Open the fctxpd.spec file in your preferred editor. Update the various versions (commit, snapshotdate etc.) and add a new entry to the %changelog section. Save the file. Create a SRPM from the changed (but not committed spec file): Oops, this was meant to say: Create a SRPM from the changed (but not committed) spec file: fedpkg srpm Run a scratch build in the koji build system: fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm Wait for the results, check them, fix any problems. Once you have a working package, commit your changes to the spec file: fedpkg new-sources NEW-UPSTREAM-TARBALL.tar.gz fedpkg commit -c And your mail software seems to have lost a newline between these two commands: fedpkg new-sources NEW-UPSTREAM-TARBALL.tar.gz fedpkg commit -c And publish them: fedpkg push And do the real build: fedpkg build I should also say that these steps are not the _only_ way to do it (they're not even the way I would do it most of the time). But they should be a simple-to-follow sequence that is relatively hard to screw up. Use 'man fedpkg' to find out more about each step, and see these links for additonal background information: https://docs.fedoraproject.org/en-US/quick-docs/creating-rpm-packages/ https://fedoraproject.org/wiki/Package_maintenance_guide https://fedoraproject.org/wiki/Package_update_HOWTO ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
RE: Query on upgrading the Fedora package
Hi Samuel, A mistake from my side . I missed checking Jonathan reply. Thanks for pointing the same. Regards, Muneendra. -Original Message- From: Samuel Sieb [mailto:sam...@sieb.net] Sent: Wednesday, July 29, 2020 11:29 AM To: Development discussions related to Fedora Cc: Muneendra Kumar M Subject: Re: Query on upgrading the Fedora package On 7/28/20 9:56 PM, Muneendra Kumar M via devel wrote: > Can anyone provide the info for the below one. Jonathan Wakely already replied with a detailed explanation. If you still have questions, you should reply to that email with some more details about what you're trying to do and what the problem is. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
RE: Query on upgrading the Fedora package
Hi Jonathan, Thanks for sharing the info. Regards, Muneendra. -Original Message- From: Jonathan Wakely [mailto:jwak...@fedoraproject.org] Sent: Tuesday, July 28, 2020 4:49 PM To: Development discussions related to Fedora Cc: Muneendra Kumar M Subject: Re: Query on upgrading the Fedora package On 28/07/20 15:05 +0530, Muneendra Kumar M via devel wrote: >Hi All, > > > >I want to upgrade the fctxpd fedora package with additional features. > >Iam the maintainer of this fctxpd package in fedora. > >Can anyone help me the procedure regarding the same. I don't know what part of the procedure you're unclear about, so here's a summary of the entire process from start to finish. Get the package sources: fedpkg clone fctxpd cd fctxpd Now download the new upstream code. Optionally verify the package was downloaded correctly by checking a SHA or other hash. Open the fctxpd.spec file in your preferred editor. Update the various versions (commit, snapshotdate etc.) and add a new entry to the %changelog section. Save the file. Create a SRPM from the changed (but not committed spec file): fedpkg srpm Run a scratch build in the koji build system: fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm Wait for the results, check them, fix any problems. Once you have a working package, commit your changes to the spec file: fedpkg new-sources NEW-UPSTREAM-TARBALL.tar.gz fedpkg commit -c And publish them: fedpkg push And do the real build: fedpkg build ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Query on upgrading the Fedora package
On 7/28/20 9:56 PM, Muneendra Kumar M via devel wrote: Can anyone provide the info for the below one. Jonathan Wakely already replied with a detailed explanation. If you still have questions, you should reply to that email with some more details about what you're trying to do and what the problem is. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
RE: Query on upgrading the Fedora package
Hi All, Can anyone provide the info for the below one. Regards, Muneendra. *From:* Muneendra Kumar M [mailto:muneendra.ku...@broadcom.com] *Sent:* Tuesday, July 28, 2020 3:05 PM *To:* 'Development discussions related to Fedora' < devel@lists.fedoraproject.org> *Subject:* Query on upgrading the Fedora package Hi All, I want to upgrade the fctxpd fedora package with additional features. Iam the maintainer of this fctxpd package in fedora. Can anyone help me the procedure regarding the same. Regards, Muneendra. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: Query on upgrading the Fedora package
On 28/07/20 15:05 +0530, Muneendra Kumar M via devel wrote: Hi All, I want to upgrade the fctxpd fedora package with additional features. Iam the maintainer of this fctxpd package in fedora. Can anyone help me the procedure regarding the same. I don't know what part of the procedure you're unclear about, so here's a summary of the entire process from start to finish. Get the package sources: fedpkg clone fctxpd cd fctxpd Now download the new upstream code. Optionally verify the package was downloaded correctly by checking a SHA or other hash. Open the fctxpd.spec file in your preferred editor. Update the various versions (commit, snapshotdate etc.) and add a new entry to the %changelog section. Save the file. Create a SRPM from the changed (but not committed spec file): fedpkg srpm Run a scratch build in the koji build system: fedpkg scratch-build --srpm $(fedpkg verrel).src.rpm Wait for the results, check them, fix any problems. Once you have a working package, commit your changes to the spec file: fedpkg new-sources NEW-UPSTREAM-TARBALL.tar.gz fedpkg commit -c And publish them: fedpkg push And do the real build: fedpkg build ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
