After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 472918 - Updatind the project version
Updatind the project version
Status: RESOLVED NOTABUG
Product: gnome-build
Classification: Deprecated
Component: libgbf_am
0.1.x
Other All
: Normal minor
: ---
Assigned To: gnome-build Maintainers List
gnome-build Maintainers List
Depends on:
Blocks:
 
 
Reported: 2007-09-02 19:22 UTC by Danilo
Modified: 2008-01-22 12:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Danilo 2007-09-02 19:22:50 UTC 
Please describe the problem:
Under menu Project -> properities when i change the version in the file configure.in change only the version in this field AC_INIT(configure.in, xxx, xxx ). But is necessary to change this field also... AM_INIT_AUTOMAKE( xxx , xxx ) .
Anjuta not update both filed but only the first... the second field will be update  by hand... 

Steps to reproduce:
1. upgrading the project version
2. 
3. 


Actual results:


Expected results:


Does this happen every time?
yes

Other information:
Comment 1 Johannes Schmid 2007-09-02 19:30:02 UTC 
Moved to gnome-build component!
Comment 2 28872d13 2008-01-21 18:43:59 UTC 
Well, I am not quite sure if this really is a bug of gnome-build. I can understand the problem, but why not simply use "AM_INIT_AUTOMAKE(AC_PACKAGE_NAME, AC_PACKAGE_VERSION)", as e.g. anjuta does by default?
Comment 3 Naba Kumar 2008-01-21 21:46:19 UTC 
(In reply to comment #2)
> Well, I am not quite sure if this really is a bug of gnome-build. I can
> understand the problem, but why not simply use
> "AM_INIT_AUTOMAKE(AC_PACKAGE_NAME, AC_PACKAGE_VERSION)", as e.g. anjuta does by
> default?
> 
I suppose that's a good way to fix it.
Comment 4 Johannes Schmid 2008-01-22 12:33:36 UTC 
OK, thanks for investigation. I think using the macros it the default way to deal with it.

=> NOTABUG