Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366827 - .spec parsing not done before %changelog entry
Summary: .spec parsing not done before %changelog entry
Status: CLOSED WONTFIX
Alias: None
Product: Linux Tools
Classification: Tools
Component: RPM (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Sami Wagiaalla CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-15 11:19 EST by Andrew Overholt CLA
Modified: 2022-10-11 05:33 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2011-12-15 11:19:41 EST 
If I make a change to the version or release in a specfile and then press Ctrl-Alt-c, the previous version (ie. the one from the saved version) is used and not the new one.
Comment 1 Neil Guzman CLA 2013-06-20 16:53:26 EDT 
this doesn't seem to occur anymore, should be closed/resolved.
Comment 2 Neil Guzman CLA 2013-10-28 17:03:46 EDT 
(In reply to Neil Guzman from comment #1)
> this doesn't seem to occur anymore, should be closed/resolved.

Actually seems to occur sometimes for changing the version number, but never when changing the release.

When changing the version (and not saving), the changelog entry will sometimes either be the new number or the previous number. However, pressing Ctrl+Alt+c 1-2 more times (still not saving) will use the new number.
Comment 3 Eclipse Genie CLA 2015-10-19 04:22:55 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2017-10-09 01:02:15 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2019-09-30 11:59:37 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Eclipse Genie CLA 2021-09-20 09:25:27 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 7 Alexander Kurtakov CLA 2022-10-11 05:33:07 EDT 
No interest in further enhancing RPM plugin.