Spec URL: https://github.com/open-power-sdk/fedora/blob/master/pveclib.spec SRPM URL: <srpm info here> Description: Power Vector Library (pveclib) A library of useful vector operations for POWER. Version 1.0.4 Multiple (128-bit) quadword multiplies and adds. Also add IFUNC enable runtime libraries to support the complex operations available from vec_int512_ppc.h More complete description and rationale here: https://github.com/open-power-sdk/pveclib/wiki License: Apache V2.0 Project governance: modified DCO 1.1 Fedora Account System Username: munroesj52
Created attachment 1700360 [details] SRPM build on F32 Cant figure out COPR yet
It is already packaged https://src.fedoraproject.org/rpms/pveclib and you are the owner. Do you require help to update it? You don't need a review for an update. 1. cd pveclib 2. fedpkg switch-branch master (Make sure our changes go to master first) 3. Edit the SPEC to update it (Don't forget to bump version-release and add the corresponding changelog entry). 4. Download the new source: spectool -g *.spec; 5. Upload the new source to dist-git (remove any old archives first if it still there) fedpkg new-sources *.tar.gz 6. Test your changes with a scratch build: fedpkg --release f33 scratch-build --srpm --fail-fast If it fails, look at the logs to understand why. 7. If it's good, remove the SRPM from your repo: rm -f *.src.rpm 8. Stage your changes git add . 9. Commit your changes: fedpkg ci -cs 10. Push fedpkg push 11. Build fedpkg build 12. Then if you want to support other branches: fedpkg switch-branch f32 13. Import your changes from master: git merge master 14. Push & build for F32: fedpkg push fedpkg build 15. Request an update from bodhi: fedpkg update --type enhancement --bugs XXXXXX (add a bug number if needed)
(In reply to Robert-André Mauchin 🐧 from comment #2) > It is already packaged https://src.fedoraproject.org/rpms/pveclib and you > are the owner. > > Do you require help to update it? You don't need a review for an update. ... > > fedpkg update --type enhancement --bugs XXXXXX (add a bug number if needed) Sorry I lost all the bread crumbs from the last time (11 months ago). So yes I could use some help. Also I need a reminder (doc link) for how to apply my pagure.keys. In the meantime I will review the fedpkg doc.
It looks like I need help: I have a Fedora 30 and 42 system. I originated pveclib for f31 from the f30 system (pagure.keys and all that). Can I continue to work fedpkg from the F30 install or do I move up to F32? Has the setup changes for F32? The pagure.keys where in .config/rpkg/fedpkg.conf. I copied fedpkg.conf from the F30 to to .config/rpkg/fedpkg.conf on the F32 system but "fedpkg clone pveclib" fails there: sjmunroe.org: Permission denied (publickey). fatal: Could not read from remote repository. hmmm: my local id is sjmunroe but my FAS login is munroesj52? So I have miss configure fedpkg on the F32 install?
(In reply to Steven Jay Munroe from comment #4) > It looks like I need help: I have a Fedora 30 and 42 system. I originated > pveclib for f31 from the f30 system (pagure.keys and all that). Can I > continue to work fedpkg from the F30 install or do I move up to F32? > > Has the setup changes for F32? The pagure.keys where in > .config/rpkg/fedpkg.conf. I copied fedpkg.conf from the F30 to to > .config/rpkg/fedpkg.conf on the F32 system but "fedpkg clone pveclib" fails > there: > > sjmunroe.org: Permission denied (publickey). > fatal: Could not read from remote repository. > > > hmmm: my local id is sjmunroe but my FAS login is munroesj52? So I have miss > configure fedpkg on the F32 install? Ok fixed the identity crisis from: https://fedoraproject.org/wiki/Package_maintenance_guide#Installing_fedpkg_and_doing_initial_setup I should be able the swing the exist pveclib-1.0.3 to F32 for build. Then update source to pveclib-1.0.4alpha2 for rawhide?
$ fedpkg --release f33 scratch-build --srpm --fail-fast setting SOURCE_DATE_EPOCH=1594080000 Wrote: /home/sjmunroe/fedora-scm/pveclib/pveclib-1.0.4alpha2-3.fc33.src.rpm [====================================] 100% 00:00:00 755.74 KiB 1.03 MiB/sec Building pveclib-1.0.4alpha2-3.fc33.src.rpm for f33-candidate Created task: 47275073 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=47275073 Watching tasks (this may be safely interrupted)... 47275073 build (f33-candidate, pveclib-1.0.4alpha2-3.fc33.src.rpm): free 47275073 build (f33-candidate, pveclib-1.0.4alpha2-3.fc33.src.rpm): free -> open (buildvm-ppc64le-38.iad2.fedoraproject.org) 47275085 rebuildSRPM (noarch): closed 47275160 buildArch (pveclib-1.0.4alpha2-3.fc33.src.rpm, ppc64le): open (buildvm-ppc64le-04.iad2.fedoraproject.org) 47275073 build (f33-candidate, pveclib-1.0.4alpha2-3.fc33.src.rpm): open (buildvm-ppc64le-38.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 1 open 1 done 1 failed 47275160 buildArch (pveclib-1.0.4alpha2-3.fc33.src.rpm, ppc64le): open (buildvm-ppc64le-04.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 2 failed 47275073 build (f33-candidate, pveclib-1.0.4alpha2-3.fc33.src.rpm) failed [sjmunroe@homer54 pveclib]$ ls clog pveclib.spec sources pveclib-1.0.4alpha2-3.fc33.src.rpm README.md v1.0.4alpha2.tar.gz soooo where do I find the build.log or root.log?
Ok this is better: fixed up typos in pveclib.spec rawhide builds for 1.0.4-alpha2 $ fedpkg build Building pveclib-1.0.4alpha2-3.fc33 for rawhide Created task: 47279676 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=47279676 Watching tasks (this may be safely interrupted)... 47279676 build (rawhide, /rpms/pveclib.git:46b3a365f589ab3c57806894db198e04961c345f): free 47279676 build (rawhide, /rpms/pveclib.git:46b3a365f589ab3c57806894db198e04961c345f): free -> open (buildhw-x86-01.iad2.fedoraproject.org) 47279705 buildSRPMFromSCM (/rpms/pveclib.git:46b3a365f589ab3c57806894db198e04961c345f): free 47279705 buildSRPMFromSCM (/rpms/pveclib.git:46b3a365f589ab3c57806894db198e04961c345f): free -> open (buildvm-s390x-08.s390.fedoraproject.org) 47279750 buildArch (pveclib-1.0.4alpha2-3.fc33.src.rpm, ppc64le): open (buildvm-ppc64le-23.iad2.fedoraproject.org) 47279705 buildSRPMFromSCM (/rpms/pveclib.git:46b3a365f589ab3c57806894db198e04961c345f): open (buildvm-s390x-08.s390.fedoraproject.org) -> closed 0 free 2 open 1 done 0 failed 47279795 tagBuild (noarch): open (buildvm-s390x-06.s390.fedoraproject.org) 47279750 buildArch (pveclib-1.0.4alpha2-3.fc33.src.rpm, ppc64le): open (buildvm-ppc64le-23.iad2.fedoraproject.org) -> closed 0 free 2 open 2 done 0 failed 47279676 build (rawhide, /rpms/pveclib.git:46b3a365f589ab3c57806894db198e04961c345f): open (buildhw-x86-01.iad2.fedoraproject.org) -> closed 0 free 1 open 3 done 0 failed 47279795 tagBuild (noarch): open (buildvm-s390x-06.s390.fedoraproject.org) -> closed 0 free 0 open 4 done 0 failed 47279676 build (rawhide, /rpms/pveclib.git:46b3a365f589ab3c57806894db198e04961c345f) completed successfully But I am just a little wierded out by the buildvm-s390x-08.s390 stuff
Please don't NEEDINFO the package reviews mailing list. It only creates more spam for an already very busy mailing list. > But I am just a little wierded out by the buildvm-s390x-08.s390 stuff You don't need to be. The tasks scheduled to run on s390x were 1) building the SRPM file and 2) tagging the package into the correct tag in koji, which are both architecture independent.
I can see pveclib-1.0.4-3.fc33 was successfully built for Fedora 33. That's all what's needed for Fedora 33. I can see pveclib-1.0.4-3.el8 and pveclib-1.0.4-3.el7 were built. To get non-Rawhide builds into a stable repository, the builds must undergo a testing. That's performed by submitting them into a updates-testing repository with "bodhi updates create ..." command or using a <https://bodhi.fedoraproject.org/updates/> web page. After undergoing a successful testing (you will be notified by an e-mail), you will be able to push them into a stable repository (again with the "bodhi updates request ..." command or with the web page). Then they will be available for all users. Since this bug report is not about a package, but about upgrading the package, I'm moving it to the pveclib component, assigning it you (because you do the upgrade), and changing the bug status to MODIFIED, because the package has already been updated in the dist-git.
(In reply to Fabio Valentini from comment #8) > Please don't NEEDINFO the package reviews mailing list. It only creates more > spam for an already very busy mailing list. > Noted thanks > > But I am just a little wierded out by the buildvm-s390x-08.s390 stuff > > You don't need to be. The tasks scheduled to run on s390x were 1) building > the SRPM file and 2) tagging the package into the correct tag in koji, which > are both architecture independent. Good to know thanks.
FEDORA-EPEL-2020-7c3fde7f74 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7c3fde7f74
FEDORA-EPEL-2020-df3af2a8f8 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-df3af2a8f8
FEDORA-EPEL-2020-df3af2a8f8 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-df3af2a8f8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-7c3fde7f74 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7c3fde7f74 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-df3af2a8f8 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-7c3fde7f74 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.