Bug 2043143 - Package note uses version/release from the last subpackage
Summary: Package note uses version/release from the last subpackage
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: package-notes
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zbigniew Jędrzejewski-Szmek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-20 17:22 UTC by Vít Ondruch
Modified: 2022-01-22 11:02 UTC (History)
2 users (show)

Fixed In Version: package-notes-0.4-9.fc36
Clone Of:
Environment:
Last Closed: 2022-01-22 11:02:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vít Ondruch 2022-01-20 17:22:23 UTC
This bug was initially created as a copy of Bug #2043092

Description of problem:
Version/Release of last subpackage is used instead of Version/Release from the main package. From the ruby-3.0.3-158.fc36 build [1]:

~~~
+ '[' -f /builddir/build/BUILD/.package_note-ruby-0.15.2-158.fc36.x86_64.ld ']'
+ '[' -f /usr/lib/rpm/generate-rpm-note.sh ']'
+ /usr/lib/rpm/generate-rpm-note.sh ruby 0.15.2-158.fc36 x86_64
~~~



Version-Release number of selected component (if applicable):
package-notes-0.4-3.fc36


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Notes are using wrong Version/Release


Expected results:
The correct Version/Release is used (or not used at all)


Additional info:



[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=81534724

Comment 1 Zbigniew Jędrzejewski-Szmek 2022-01-20 19:57:38 UTC
I admit I no idea how to approach this. I assumed that %name and %version are a pair that can be relied on.
I think we want the original srpm name and version to be used in the notes. Is there some rpm macro
that stores the original %version?

Comment 2 Zbigniew Jędrzejewski-Szmek 2022-01-20 21:07:26 UTC
https://src.fedoraproject.org/rpms/package-notes/pull-request/1


Note You need to log in before you can comment on or make changes to this bug.