#12262 Issue about building package with side tag of f42-build-side-94214 on f41 branch
Closed: It's all good a month ago by kevin. Opened a month ago by topazus.

  • Describe the issue

A few moments ago, I decided to update the deepin-dock to 6.0.37. So I should commit the changes to rawhide first and build the deepin-dock package with the side tag of f42-build-side-94214 on rawhide, which I accidentaly and wrongly committed to f41 branch first and build it with fedpkg build --target=f42-build-side-94214. [1,2] Here is the following output of related commands:

Uploading: /home/aurora/rpmbuild/SOURCES/dde-dock-6.0.37.tar.gz to https://src.fedoraproject.org/repo/pkgs/upload.cgi
Uploading: /home/aurora/rpmbuild/SOURCES/dde-dock-6.0.37.tar.gz
######################################################################## 100.0%
Source upload succeeded. Don't forget to commit the sources file
[f41 738011c] 6.0.37
 3 files changed, 71 insertions(+), 64 deletions(-)
Enumerating objects: 9, done.
Counting objects: 100% (9/9), done.
Delta compression using up to 20 threads
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 1.48 KiB | 1.48 MiB/s, done.
Total 5 (delta 2), reused 0 (delta 0), pack-reused 0 (from 0)
remote: Emitting a message to the fedora-messaging message bus.
remote: * Publishing information for 1 commits
remote: Sending to redis to log activity and send commit notification emails
remote: * Publishing information for 1 commits
remote:   - to fedora-message
remote: 2024-08-15 12:17:13,346 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive
remote: 
remote: Create a pull-request for f41
remote:    https://src.fedoraproject.org/rpms/deepin-dock/diff/rawhide..f41
remote: 
To ssh://pkgs.fedoraproject.org/rpms/deepin-dock
   5497530..738011c  f41 -> f41
Building deepin-dock-6.0.37-1.fc41 for f42-build-side-94214
Created task: 121981027
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=121981027
Watching tasks (this may be safely interrupted)...
121981027 build (f42-build-side-94214, /rpms/deepin-dock.git:738011ccf99afcdad24a24e6138d52f5640fed6d): free
121981027 build (f42-build-side-94214, /rpms/deepin-dock.git:738011ccf99afcdad24a24e6138d52f5640fed6d): free -> open (buildhw-a64-12.iad2.fedoraproject.org)
  121981059 buildSRPMFromSCM (/rpms/deepin-dock.git:738011ccf99afcdad24a24e6138d52f5640fed6d): free

The f41 branch is one commit ahead of rawhide branch, the koji build results showed it has built packages that has name, like deepin-dock-6.0.37-1.fc42.x86_64.rpm. The root.log file of koji build indicated it was built on f42.

[1] https://src.fedoraproject.org/rpms/deepin-dock/commits/rawhide
[2] https://src.fedoraproject.org/rpms/deepin-dock/commits/f41
[3] https://koji.fedoraproject.org/koji/taskinfo?taskID=121981027

  • When do you need this? (YYYY/MM/DD)

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?


Right, you can build any valid release from any valid branch.

So, I would suggest untagging those builds from your side tag and merging your commit to rawhide branch in git and doing some new builds (you can re-use the sidetag).
Then, if you want to build for f41, do a new set of builds there.

Does that sound reasonable?

If you need us to do anything here, please reopen... thanks!

Metadata Update from @kevin:
- Issue close_status updated to: It's all good
- Issue status updated to: Closed (was: Open)

a month ago

Log in to comment on this ticket.

Metadata